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!

Persistent Queue at TcpOut — One of Splunk's Most Practical Features

Splunk introduced persistent queueing at the tcpout layer as one of the most practical resilience features in ...

Skip the Awkward Silence: Have a .conf-ersation at .conf26

Picture this. You arrive at .conf26 already having your socializing and networking plans mapped out. No ...

Rethinking Zero Trust: From Product Purchases to Logical Control Evidence

Implementing Zero Trust (ZT) across complex environments often falters at the very beginning due to a ...