Automated Multi-Standard Compliance Scan
Budget: $30 – $250 USD
I have supplied two reference files: a short requirements document that spells out the scan logic and an HTML template that shows exactly how the finished report must look. What I need is a small, self-contained utility that I can launch from a Linux jump box to sweep our internal subnets, evaluate each host against the controls in the document, and then generate the same HTML report automatically.
The scan has to map findings to every framework listed below so I can demonstrate unified compliance in one pass:
• NIST SP 800-53 Rev 5
• CIS Benchmarks
• DISA STIG
• Risk Management Framework (RMF) mappings
• CJIS
• PCI
• OMB 130
• FIPS 199 & 200
Open-source tooling is preferred—feel free to orchestrate Nmap, OpenVAS, or similar scanners in the background—but the final workflow must be driven by a single command-line script or binary with a clear README. When it runs, it should:
1. Discover live hosts from a list of CIDRs I supply.
2. Execute the checks defined in the requirements document.
3. Translate raw findings into the control language of each framework above.
4. Populate the provided HTML template with pass/fail status, evidence snippets, and a timestamp.
Acceptance criteria
• One-step execution: `./netscan.sh -c config.yml` (or equivalent) produces the HTML report with no manual edits.
• Report layout, colours, section order, and file name match the template byte-for-byte except for populated data.
• Code is clean, commented, and delivered in a single archive or Git repository.
If anything in the requirements document is unclear, call it out before you start so we can lock it down early. Looking forward to a concise, well-documented solution that I can drop into production with minimal tweaks.
The scan has to map findings to every framework listed below so I can demonstrate unified compliance in one pass:
• NIST SP 800-53 Rev 5
• CIS Benchmarks
• DISA STIG
• Risk Management Framework (RMF) mappings
• CJIS
• PCI
• OMB 130
• FIPS 199 & 200
Open-source tooling is preferred—feel free to orchestrate Nmap, OpenVAS, or similar scanners in the background—but the final workflow must be driven by a single command-line script or binary with a clear README. When it runs, it should:
1. Discover live hosts from a list of CIDRs I supply.
2. Execute the checks defined in the requirements document.
3. Translate raw findings into the control language of each framework above.
4. Populate the provided HTML template with pass/fail status, evidence snippets, and a timestamp.
Acceptance criteria
• One-step execution: `./netscan.sh -c config.yml` (or equivalent) produces the HTML report with no manual edits.
• Report layout, colours, section order, and file name match the template byte-for-byte except for populated data.
• Code is clean, commented, and delivered in a single archive or Git repository.
If anything in the requirements document is unclear, call it out before you start so we can lock it down early. Looking forward to a concise, well-documented solution that I can drop into production with minimal tweaks.
Related categories:
Linux
HTML
Compliance
Risk Management
Penetration Testing
Scripting
Documentation
Automation