Linux Auditd Possible Access Or Modification Of Sshd Config File

Original Source: [splunk source]
Name:Linux Auditd Possible Access Or Modification Of Sshd Config File
id:acb3ea33-70f7-47aa-b335-643b3aebcb2f
version:2
date:2024-09-30
author:Teoderick Contreras, Splunk
status:production
type:Anomaly
Description:The following analytic detects suspicious access or modification of the sshd_config file on Linux systems. It leverages data from Linux Auditd, focusing on command-line executions involving processes like "cat," "nano," "vim," and "vi" accessing the sshd_config file. This activity is significant because unauthorized changes to sshd_config can allow threat actors to redirect port connections or use unauthorized keys, potentially compromising the system. If confirmed malicious, this could lead to unauthorized access, privilege escalation, or persistent backdoor access, posing a severe security risk.
Data_source:
  • -Linux Auditd Path
search:`linux_auditd` type=PATH name="/etc/ssh/ssh_config*"
| rename host as dest
| stats count min(_time) as firstTime max(_time) as lastTime by name nametype OGID type dest
| `security_content_ctime(firstTime)`| `security_content_ctime(lastTime)`| `linux_auditd_possible_access_or_modification_of_sshd_config_file_filter`


how_to_implement:To implement this detection, the process begins by ingesting auditd data, that consist SYSCALL, TYPE, EXECVE and PROCTITLE events, which captures command-line executions and process details on Unix/Linux systems. These logs should be ingested and processed using Splunk Add-on for Unix and Linux (https://splunkbase.splunk.com/app/833), which is essential for correctly parsing and categorizing the data. The next step involves normalizing the field names to match the field names set by the Splunk Common Information Model (CIM) to ensure consistency across different data sources and enhance the efficiency of data modeling. This approach enables effective monitoring and detection of linux endpoints where auditd is deployed
known_false_positives:Administrator or network operator can use this commandline for automation purposes. Please update the filter macros to remove false positives.
References:
  -https://www.hackingarticles.in/ssh-penetration-testing-port-22/
  -https://attack.mitre.org/techniques/T1098/004/
drilldown_searches:
name:'View the detection results for - "$dest$"'
search:'%original_detection_search% | search dest = "$dest$"'
earliest_offset:'$info_min_time$'
latest_offset:'$info_max_time$'
name:'View risk events for the last 7 days for - "$dest$"'
search:'| from datamodel Risk.All_Risk | search normalized_risk_object IN ("$dest$") starthoursago=168 | stats count min(_time) as firstTime max(_time) as lastTime values(search_name) as "Search Name" values(risk_message) as "Risk Message" values(analyticstories) as "Analytic Stories" values(annotations._all) as "Annotations" values(annotations.mitre_attack.mitre_tactic) as "ATT&CK Tactics" by normalized_risk_object | `security_content_ctime(firstTime)` | `security_content_ctime(lastTime)`'
earliest_offset:'$info_min_time$'
latest_offset:'$info_max_time$'
tags:
  analytic_story:
    - 'Linux Living Off The Land'
    - 'Linux Privilege Escalation'
    - 'Linux Persistence Techniques'
    - 'Compromised Linux Host'
  asset_type:Endpoint
  confidence:50
  impact:50
  message:A [$type$] has been accessed/modified on host - [$dest$] to modify the sshd_config file.
  mitre_attack_id:
    - 'T1098.004'
    - 'T1098'
  observable:
    name:'dest'
    type:'Endpoint'
    - role:
      - 'Victim'
  product:
    - 'Splunk Enterprise'
    - 'Splunk Enterprise Security'
    - 'Splunk Cloud'
  required_fields:
    - '_time'
    - 'name'
    - 'nametype'
    - 'OGID'
  risk_score:25
  security_domain:endpoint

tests:
name:'True Positive Test'
 attack_data:
  data: https://media.githubusercontent.com/media/splunk/attack_data/master/datasets/attack_techniques/T1098.004/linux_auditd_nopasswd/linux_auditd_ssh_config.log
  source: /var/log/audit/audit.log
  sourcetype: linux:audit
manual_test:None