Monitoring command line interface actions

Scenario: Your Security Operations manager has requested that you monitor command line actions of users in your organization. They haven't specified exactly what you should set alerts for, but you know that the MITRE ATT&CK framework lists more than 150 attacks associated with the command line. 

How Splunk software can help

You can use Splunk software to view command line strings, calculate their length to evaluate them against others in their peer groups, and determine how much time has passed since their related processes ran.

What you need 

To succeed in implementing this use case, you need the following dependencies, resources, and information.

People

The best person to implement this use case is a security analyst who is familiar with Microsoft Sysmon and Windows event logs. This person might come from your team, a Splunk partner, or Splunk onDemand Services.

Time

Configuring an alert or monitoring a dashboard can take less than 10 minutes, but adjusting the alert thresholds to meet the needs of your organization can add time.

Technologies 

The following technologies, data, and integrations are useful in successfully implementing this use case: 

• Splunk Enterprise or Splunk Cloud
• Data sources onboarded
  • Operating system event data

How to use Splunk software for this use case

You can run many searches with Splunk software on command line strings. Depending on what information you have available, you might find it useful to do some or all of the following: 

• Determine the length of command line strings
• Determine how much time has passed since a string executed
• Convert strings to a common format 
• Previously seen command line argument
• First time seen command line argument

Other steps you can take

To maximize their benefit, the how-to articles linked in the previous section likely need to tie into existing processes at your organization or become new standard processes. These processes commonly impact success with this use case: 

• Enabling self-protection so that CLI commands must include the authentication password
• Requiring the use of libraries or APIs for commands
• Providing whitelists or other mechanisms for input validation

How to assess your results

Measuring impact and benefit is critical to assessing the value of security operations. The following are example metrics that can be useful to monitor when implementing this use case:

• CLI execution attacks detected: The number of true positive malicious CLI executions detected using Splunk software