Comments on: Linux STIG SRR Viewer

By: Peter D

Peter D — Thu, 25 Aug 2011 01:15:56 +0000

This was great when it came out but now that there is Vulnerator which does Retina, Gold Disk, UNIX SRR, LINUX/ESX SRR and SQL SRR there is no longer a need for this tool.

By: Chris C

Chris C — Tue, 29 Mar 2011 16:36:07 +0000

If you are willing to pay there is a company called prolific-solutions that makes a product called proVM that will consolidate findings from the gold disk, srr(s), nessus, app detective, and some other tools for you. It produces some really easy to read spreadsheets. I have used it in support of my programs and it has been very useful.

By: Gary Asp

Gary Asp — Wed, 23 Mar 2011 21:49:14 +0000

Lee – when you say I need to check the first few pages of the results, are you talking about the xml file or….?

By: Linux STIG SRR Viewer (Version 2)

Linux STIG SRR Viewer (Version 2) — Fri, 28 Jan 2011 01:43:17 +0000

[...] updated the Linux STIG SRR Viewer originally released here to incorporate some of the community [...]

By: AgintOring

AgintOring — Thu, 27 Jan 2011 20:10:52 +0000

Looks like closed perenthesese “)” are not handled properly when exporting to a CSV.

I noticed the “Results” for V0000903 carried across 6 columns instead of 2 and the break point appears to be the close paren…

In anycase. Great job!

By: Lee Mangold

Lee Mangold — Sun, 16 Jan 2011 23:35:33 +0000

All –

I worked with Gary Asp (above) on this issue and we found that the SRR appeared to be placing control characters of some sort in the results file. While I should handle these eventualities better, this may also be a bug in the SRR; I haven’t had the time to fully test though.

If you see these issues, check the first few pages of results for strange characters, delete, and re-load in the STIG Viewer app. This is a stop-gap until I can get around to handling the error more gracefully…

By: Gary Asp

Gary Asp — Tue, 04 Jan 2011 15:43:28 +0000

Lee – I’ve used your tool multiple times before, so I don’t believe it is user error. I’m using the October 29, 2010 SRR Script. I copied the PDI-DB file into the root of the results folder after running the SRR tool against my system. Have you ever seen your tool throw this error:

Unhandled exception has occurred in your application. If you click Continue, the application will ignore this error and attempt to continue. if you click Quit, the application will close immediately.
‘[]‘, hexadecimal value 0x1B, is an invalid character. Line 75, position 94.

By: Lee Mangold

Lee Mangold — Fri, 05 Nov 2010 12:16:11 +0000

RC -
The only trick is sourcing the PDI-DB file. You can get that file out of the root of the Unix SRR script package. I can’t post it here, unfortunately.

I’m thinking about creating a POA&M export tool to add into this…should be easy, but I just have to find the time!

By: RC

RC — Thu, 04 Nov 2010 17:39:49 +0000

It would be nice to have a How to Document with this one. I’ll try it at home..too much work

Yhanks for coming up with this tool. I’ll let you know.

By: Tim

Tim — Sat, 10 Jul 2010 19:20:38 +0000

I am going to have to try this and will let you know how it works