Getting Data In

help with SEDCMD

jambajuice
Communicator

I'm trying to clean up events from a Nessus 4 NBE file. Sample results look like the following:

results|192.168.2|192.168.2.183|compaq-https (2381/tcp)|40406|Security Note|Synopsis :\n\nNessus encountered errors while running its generic CGI attacks.\n\nDescription :\n\nNessus ran into trouble while running its generic CGI tests against\nthe remote web server (for example, connection refused, timeout, etc). \nWhen this happens, Nessus aborts the current test and switches to the\nnext CGI script on the same port or to another web server.  Thus, test\nresults may be incomplete.\n\nSolution :\n\nRescan with a longer network timeout or less parallelism for example,\nby changing the following options in the scan policy :\n\n  - Network -> Network Receive Timeout (check_read_timeout)\n\n  - Options -> Number of hosts in parallel (max_hosts)\n\n  - Options -> Number of checks in parallel (max_checks)\n\nRisk factor :\n\nNone\n\nPlugin output :\n\nNessus encountered :\n\n  - 1 error involving SQL injection (on HTTP headers) checks.\n\n

I would like to replace every instance of \n with a space. My props.conf looks like this:

[nessus]
BREAK_ONLY_BEFORE = results|
SEDCMD-newline = s/\\n//

What am I doing wrong here?

Thx.

Craig

Tags (1)
0 Karma

araitz
Splunk Employee
Splunk Employee

Maybe:

[nessus]
BREAK_ONLY_BEFORE = results|
SEDCMD-newline = s/\\n/\ /

Or:

[nessus]
BREAK_ONLY_BEFORE = results|
SEDCMD-newline = s/\\n/ /

ftk
Motivator

your second config is correct.

0 Karma
Got questions? Get answers!

Join the Splunk Community Slack to learn, troubleshoot, and make connections with fellow Splunk practitioners in real time!

Meet up IRL or virtually!

Join Splunk User Groups to connect and learn in-person by region or remotely by topic or industry.

Get Updates on the Splunk Community!

Your Feedback. Our Roadmap. Visit the PX Feedback Booth at .conf26

You use Splunk every day, come and help shape what's next.  Save Your Seat: Product-Focused Sessions at ...

Agentic SOC Triage: Investigating Splunk ES Notables with MCP Server and a Local LLM

The Problem: Too Many Alerts, Too Little Context Security operations teams running Splunk Enterprise Security ...

Painting a Clearer Picture: Creating Cross-Domain Visibility with AI Canvas

Watch Now Painting a Clearer Picture: Creating Cross-Domain Visibility with AI Canvas     Do you ever feel ...