Ekinops OneOS
Overview
Ekinops OneOS is a comprehensive and flexible network operating system designed to meet the evolving needs of modern telecommunications networks. It provides a unified platform for managing and orchestrating a wide range of network functions, including routing, switching, security, and more. With its modular architecture and open APIs, OneOS enables network operators to easily deploy and scale their networks, while also providing the flexibility to integrate with third-party applications and services. This allows for greater innovation and agility in network operations, ultimately leading to improved service delivery and customer satisfaction.
- Vendor: Ekinops
- Supported environment: On prem
- Version Compatibility: 6 R13.0
- Detection based on: Telemetry
Configure
This setup guide will show you how to forward your Ekinops OneOS logs to Sekoia.io by means of a syslog transport channel.
Prerequisites
- Have an internal log concentrator
Enable Syslog forwarding logs
To enable syslog forwarding logs, you must follow the steps below:
- Connect on the Ekinops OneOS console
- Add the log concentrator as a new syslog server
localhost#configure terminal Enter configuration commands, one per line. End with CNTL/Z. localhost(config)#syslog server <log concentrator server ip> 23 tcp <log concentrator port> localhost(config)#logging syslog filter all localhost(config)#logging syslog informational localhost(config)#end localhost#write mem - Check the configuration
localhost#show syslog servers S.No Syslog Server Facility VrfName Protocol port Interface Bytes-Sent 1 <log concentrator server ip> 23 default - exit the console
Create the intake
Go to the intake page and create a new intake from the format Ekinops OneOS.
Forward logs to Sekoia.io
Please consult the Syslog Forwarding documentation to forward these logs to Sekoia.io.
Raw Events Samples
In this section, you will find examples of raw logs as generated natively by the source. These examples are provided to help integrators understand the data format before ingestion into Sekoia.io. It is crucial for setting up the correct parsing stages and ensuring that all relevant information is captured.
Feb 7 13:43:37 localhost : #INFO# Use of 'save running-config' by user 'admin' from Local Console on Wed Feb 07 13:43:36 UTC 2024
Feb 7 13:50:57 localhost : #INFO# Configuration modified by user 'admin' from Local Console on Wed Feb 07 13:50:55 UTC 2024
Feb 7 13:51:51 localhost : #NOTIFY# Enabled "logging syslog filter all" by user 'admin' from Local Console on Wed Feb 07 13:51:50 UTC 2024
Feb 7 13:59:14 localhost : #WARN# New RSA Crypto Key Pair Generated by user 'admin' from Local Console on Wed Feb 07 13:59:13 UTC 2024
Feb 7 13:59:22 localhost : #WARN# SSH 2.0 server has been enabled by VTY user 'admin' from Local Console at 13:59:20 Wed Feb 7 2024
Feb 7 15:40:11 localhost : #NOTIFY# IF: GigabitEthernet 0/0 is administratively UP
Feb 7 15:40:11 localhost : #NOTIFY# IF: GigabitEthernet 0/0 is UP
Feb 7 13:58:11 localhost : #NOTIFY# LOGIN_SUCCESS for VTY user 'admin' from Local Console at 13:58:09 Wed Feb 7 2024
Feb 7 13:58:07 localhost : #WARN# LOGIN_FAILURE for VTY user 'admin' from Local Console at 13:58:05 Wed Feb 7 2024
Feb 7 14:46:37 localhost : #NOTIFY# Logged out user:admin from a ssh session with client ip: 1.2.3.4 on Wed Feb 07 14:46:35 UTC 2024
Feb 7 15:40:11 localhost : #NOTIFY# ZTP [APP] Initiating zerotouch provisioning mechanism
Feb 7 15:40:11 localhost : #NOTIFY# CWMP [EVENT] Reading data from file.
Feb 7 13:50:57 localhost : #INFO# list ACL-WAN-IN denied udp 0.0.0.0:547-> 5.6.7.8:546 3 matches
Feb 7 13:50:57 localhost : #INFO# list ACL-WAN-OUT permitted proto 9 0.0.0.0:547-> 5.6.7.8:546 11 matches
Detection section
The following section provides information for those who wish to learn more about the detection capabilities enabled by collecting this intake. It includes details about the built-in rule catalog, event categories, and ECS fields extracted from raw events. This is essential for users aiming to create custom detection rules, perform hunting activities, or pivot in the events page.
Related Built-in Rules
The following Sekoia.io built-in rules match the intake Ekinops OneOS. This documentation is updated automatically and is based solely on the fields used by the intake which are checked against our rules. This means that some rules will be listed but might not be relevant with the intake.
SEKOIA.IO x Ekinops OneOS on ATT&CK Navigator
Cryptomining
Detection of domain names potentially related to cryptomining activities.
- Effort: master
Dynamic DNS Contacted
Detect communication with dynamic dns domain. This kind of domain is often used by attackers. This rule can trigger false positive in non-controlled environment because dynamic dns is not always malicious.
- Effort: master
Exfiltration Domain
Detects traffic toward a domain flagged as a possible exfiltration vector.
- Effort: master
Internet Scanner
Detects known scanner IP addresses. Alert is only raised when the scan hits an opened port, on TCP or UDP. This could be a very noisy rule, so be careful to check your detection perimeter before activation.
- Effort: master
Internet Scanner Target
Detects known scanner IP addresses. Alert is only raised when the scan hits an opened port, on TCP or UDP and group by target address. This could be a very noisy rule, so be careful to check your detection perimeter before activation.
- Effort: master
RSA SecurID Failed Authentification
Detects many failed attempts to authenticate followed by a successfull login for a super admin account.
- Effort: advanced
Remote Access Tool Domain
Detects traffic toward a domain flagged as a Remote Administration Tool (RAT).
- Effort: master
SEKOIA.IO Intelligence Feed
Detect threats based on indicators of compromise (IOCs) collected by SEKOIA's Threat and Detection Research team.
- Effort: elementary
Sekoia.io EICAR Detection
Detects observables in Sekoia.io CTI tagged as EICAR, which are fake samples meant to test detection.
- Effort: master
TOR Usage
Detects TOR usage, based on the IP address and the destination port (filtered on NTP). TOR is short for The Onion Router, and it gets its name from how it works. TOR intercepts the network traffic from one or more apps on user’s computer, usually the user web browser, and shuffles it through a number of randomly-chosen computers before passing it on to its destination. This disguises user location, and makes it harder for servers to pick him/her out on repeat visits, or to tie together separate visits to different sites, this making tracking and surveillance more difficult. Before a network packet starts its journey, user’s computer chooses a random list of relays and repeatedly encrypts the data in multiple layers, like an onion. Each relay knows only enough to strip off the outermost layer of encryption, before passing what’s left on to the next relay in the list.
- Effort: master
TOR Usage Generic Rule
Detects TOR usage globally, whether the IP is a destination or source. TOR is short for The Onion Router, and it gets its name from how it works. TOR intercepts the network traffic from one or more apps on user’s computer, usually the user web browser, and shuffles it through a number of randomly-chosen computers before passing it on to its destination. This disguises user location, and makes it harder for servers to pick him/her out on repeat visits, or to tie together separate visits to different sites, this making tracking and surveillance more difficult. Before a network packet starts its journey, user’s computer chooses a random list of relays and repeatedly encrypts the data in multiple layers, like an onion. Each relay knows only enough to strip off the outermost layer of encryption, before passing what’s left on to the next relay in the list.
- Effort: master
Event Categories
The following table lists the data source offered by this integration.
| Data Source | Description |
|---|---|
Network device logs |
Logs are typically coming from the OneOS network |
Authentication logs |
Log in/Log out logs |
Host network interface |
Some interface logs |
In details, the following table denotes the type of events produced by this integration.
| Name | Values |
|---|---|
| Kind | `` |
| Category | authentication, configuration, host, network, process |
| Type | change, end, info, start |
Transformed Events Samples after Ingestion
This section demonstrates how the raw logs will be transformed by our parsers. It shows the extracted fields that will be available for use in the built-in detection rules and hunting activities in the events page. Understanding these transformations is essential for analysts to create effective detection mechanisms with custom detection rules and to leverage the full potential of the collected data.
{
"message": "Feb 7 13:43:37 localhost : #INFO# Use of 'save running-config' by user 'admin' from Local Console on Wed Feb 07 13:43:36 UTC 2024",
"event": {
"category": [
"configuration"
],
"reason": "Use of 'save running-config'",
"type": [
"change"
]
},
"@timestamp": "2024-02-07T13:43:37Z",
"log": {
"level": "INFO"
},
"observer": {
"product": "OneOS",
"vendor": "Ekinops"
},
"related": {
"user": [
"admin"
]
},
"user": {
"name": "admin"
}
}
{
"message": "Feb 7 13:50:57 localhost : #INFO# Configuration modified by user 'admin' from Local Console on Wed Feb 07 13:50:55 UTC 2024",
"event": {
"category": [
"configuration"
],
"reason": "Configuration modified",
"type": [
"change"
]
},
"@timestamp": "2024-02-07T13:50:57Z",
"log": {
"level": "INFO"
},
"observer": {
"product": "OneOS",
"vendor": "Ekinops"
},
"related": {
"user": [
"admin"
]
},
"user": {
"name": "admin"
}
}
{
"message": "Feb 7 13:51:51 localhost : #NOTIFY# Enabled \"logging syslog filter all\" by user 'admin' from Local Console on Wed Feb 07 13:51:50 UTC 2024",
"event": {
"category": [
"configuration"
],
"reason": "Enabled \"logging syslog filter all\"",
"type": [
"change"
]
},
"@timestamp": "2024-02-07T13:51:51Z",
"log": {
"level": "NOTIFY"
},
"observer": {
"product": "OneOS",
"vendor": "Ekinops"
},
"related": {
"user": [
"admin"
]
},
"user": {
"name": "admin"
}
}
{
"message": "Feb 7 13:59:14 localhost : #WARN# New RSA Crypto Key Pair Generated by user 'admin' from Local Console on Wed Feb 07 13:59:13 UTC 2024",
"event": {
"category": [
"configuration"
],
"reason": " New RSA Crypto Key Pair Generated",
"type": [
"change"
]
},
"@timestamp": "2024-02-07T13:59:14Z",
"log": {
"level": "WARN"
},
"observer": {
"product": "OneOS",
"vendor": "Ekinops"
},
"related": {
"user": [
"admin"
]
},
"user": {
"name": "admin"
}
}
{
"message": "Feb 7 13:59:22 localhost : #WARN# SSH 2.0 server has been enabled by VTY user 'admin' from Local Console at 13:59:20 Wed Feb 7 2024",
"event": {
"category": [
"configuration"
],
"reason": "SSH 2.0 server has been enabled",
"type": [
"change"
]
},
"@timestamp": "2024-02-07T13:59:22Z",
"ekinops": {
"oneos": {
"origin": "VTY"
}
},
"log": {
"level": "WARN"
},
"observer": {
"product": "OneOS",
"vendor": "Ekinops"
},
"related": {
"user": [
"admin"
]
},
"user": {
"name": "admin"
}
}
{
"message": "Feb 7 15:40:11 localhost : #NOTIFY# IF: GigabitEthernet 0/0 is administratively UP",
"event": {
"action": "UP",
"category": [
"host"
],
"type": [
"change"
]
},
"@timestamp": "2024-02-07T15:40:11Z",
"log": {
"level": "NOTIFY"
},
"observer": {
"ingress": {
"interface": {
"name": "GigabitEthernet 0/0"
}
},
"product": "OneOS",
"vendor": "Ekinops"
}
}
{
"message": "Feb 7 15:40:11 localhost : #NOTIFY# IF: GigabitEthernet 0/0 is UP",
"event": {
"action": "UP",
"category": [
"host"
],
"type": [
"change"
]
},
"@timestamp": "2024-02-07T15:40:11Z",
"log": {
"level": "NOTIFY"
},
"observer": {
"ingress": {
"interface": {
"name": "GigabitEthernet 0/0"
}
},
"product": "OneOS",
"vendor": "Ekinops"
}
}
{
"message": "Feb 7 13:58:11 localhost : #NOTIFY# LOGIN_SUCCESS for VTY user 'admin' from Local Console at 13:58:09 Wed Feb 7 2024",
"event": {
"category": [
"authentication"
],
"outcome": "LOGIN_SUCCESS",
"type": [
"start"
]
},
"@timestamp": "2024-02-07T13:58:11Z",
"ekinops": {
"oneos": {
"origin": "VTY"
}
},
"log": {
"level": "NOTIFY"
},
"observer": {
"product": "OneOS",
"vendor": "Ekinops"
},
"related": {
"user": [
"admin"
]
},
"user": {
"name": "admin"
}
}
{
"message": "Feb 7 13:58:07 localhost : #WARN# LOGIN_FAILURE for VTY user 'admin' from Local Console at 13:58:05 Wed Feb 7 2024",
"event": {
"category": [
"authentication"
],
"outcome": "LOGIN_FAILURE",
"type": [
"start"
]
},
"@timestamp": "2024-02-07T13:58:07Z",
"ekinops": {
"oneos": {
"origin": "VTY"
}
},
"log": {
"level": "WARN"
},
"observer": {
"product": "OneOS",
"vendor": "Ekinops"
},
"related": {
"user": [
"admin"
]
},
"user": {
"name": "admin"
}
}
{
"message": "Feb 7 14:46:37 localhost : #NOTIFY# Logged out user:admin from a ssh session with client ip: 1.2.3.4 on Wed Feb 07 14:46:35 UTC 2024",
"event": {
"category": [
"authentication"
],
"type": [
"end"
]
},
"@timestamp": "2024-02-07T14:46:37Z",
"ekinops": {
"oneos": {
"origin": "ssh"
}
},
"log": {
"level": "NOTIFY"
},
"observer": {
"product": "OneOS",
"vendor": "Ekinops"
},
"related": {
"ip": [
"1.2.3.4"
],
"user": [
"admin"
]
},
"source": {
"address": "1.2.3.4",
"ip": "1.2.3.4"
},
"user": {
"name": "admin"
}
}
{
"message": "Feb 7 15:40:11 localhost : #NOTIFY# ZTP [APP] Initiating zerotouch provisioning mechanism",
"event": {
"category": [
"process"
],
"provider": "ZTP",
"reason": "Initiating zerotouch provisioning mechanism",
"type": [
"info"
]
},
"@timestamp": "2024-02-07T15:40:11Z",
"log": {
"level": "NOTIFY"
},
"observer": {
"product": "OneOS",
"vendor": "Ekinops"
}
}
{
"message": "Feb 7 15:40:11 localhost : #NOTIFY# CWMP [EVENT] Reading data from file.",
"event": {
"category": [
"process"
],
"provider": "CWMP",
"reason": "Reading data from file.",
"type": [
"info"
]
},
"@timestamp": "2024-02-07T15:40:11Z",
"log": {
"level": "NOTIFY"
},
"observer": {
"product": "OneOS",
"vendor": "Ekinops"
}
}
{
"message": "Feb 7 13:50:57 localhost : #INFO# list ACL-WAN-IN denied udp 0.0.0.0:547-> 5.6.7.8:546 3 matches",
"event": {
"action": "denied",
"category": [
"network"
],
"type": [
"denied"
]
},
"@timestamp": "2024-02-07T13:50:57Z",
"destination": {
"address": "5.6.7.8",
"ip": "5.6.7.8",
"port": 546
},
"log": {
"level": "INFO"
},
"network": {
"transport": "udp"
},
"observer": {
"product": "OneOS",
"vendor": "Ekinops"
},
"related": {
"ip": [
"0.0.0.0",
"5.6.7.8"
]
},
"rule": {
"name": "ACL-WAN-IN"
},
"source": {
"address": "0.0.0.0",
"ip": "0.0.0.0",
"port": 547
}
}
{
"message": "Feb 7 13:50:57 localhost : #INFO# list ACL-WAN-OUT permitted proto 9 0.0.0.0:547-> 5.6.7.8:546 11 matches",
"event": {
"action": "permitted",
"category": [
"network"
],
"type": [
"allowed"
]
},
"@timestamp": "2024-02-07T13:50:57Z",
"destination": {
"address": "5.6.7.8",
"ip": "5.6.7.8",
"port": 546
},
"log": {
"level": "INFO"
},
"network": {
"iana_number": "9"
},
"observer": {
"product": "OneOS",
"vendor": "Ekinops"
},
"related": {
"ip": [
"0.0.0.0",
"5.6.7.8"
]
},
"rule": {
"name": "ACL-WAN-OUT"
},
"source": {
"address": "0.0.0.0",
"ip": "0.0.0.0",
"port": 547
}
}
Extracted Fields
The following table lists the fields that are extracted, normalized under the ECS format, analyzed and indexed by the parser. It should be noted that infered fields are not listed.
| Name | Type | Description |
|---|---|---|
@timestamp |
date |
Date/time when the event originated. |
destination.ip |
ip |
IP address of the destination. |
destination.port |
long |
Port of the destination. |
ekinops.oneos.origin |
keyword |
Origin of the event |
event.action |
keyword |
The action captured by the event. |
event.category |
keyword |
Event category. The second categorization field in the hierarchy. |
event.outcome |
keyword |
The outcome of the event. The lowest level categorization field in the hierarchy. |
event.provider |
keyword |
Source of the event. |
event.reason |
keyword |
Reason why this event happened, according to the source |
event.type |
keyword |
Event type. The third categorization field in the hierarchy. |
log.level |
keyword |
Log level of the log event. |
network.iana_number |
keyword |
IANA Protocol Number. |
network.transport |
keyword |
Protocol Name corresponding to the field iana_number. |
observer.ingress.interface.name |
keyword |
Interface name |
observer.product |
keyword |
The product name of the observer. |
observer.vendor |
keyword |
Vendor name of the observer. |
rule.name |
keyword |
Rule name |
source.ip |
ip |
IP address of the source. |
source.port |
long |
Port of the source. |
user.name |
keyword |
Short name or login of the user. |
For more information on the Intake Format, please find the code of the Parser, Smart Descriptions, and Supported Events here.