Bug 1472282 - [RFE] Support configuration compliance scan with any security profile
[RFE] Support configuration compliance scan with any security profile
Status: NEW
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: atomic (Show other bugs)
7.5
Unspecified Unspecified
unspecified Severity unspecified
: rc
: ---
Assigned To: Lokesh Mandvekar
atomic-bugs@redhat.com
: Extras, FutureFeature
Depends On: 1471672
Blocks: 1499257
  Show dependency treegraph
 
Reported: 2017-07-18 07:07 EDT by Jan Černý
Modified: 2017-10-19 07:37 EDT (History)
5 users (show)

See Also:
Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
: 1499257 (view as bug list)
Environment:
Last Closed:
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Jan Černý 2017-07-18 07:07:12 EDT
Description of problem:
Atomic scan should scan containers and images for compliance with any security profile, for example PCI-DSS, STIG, USGCB, and others that are available in SCAP Security Guide. Atomic Scan must also be able to support customized profiles that customers have created using Red Hat supplied tools (eg. SCAP Workbench).
Atomic scan must display a detailed report.

Version-Release number of selected component (if applicable):


How reproducible:
always

Steps to Reproduce:
1. atomic scan [image/container]

Actual results:
Now atomic scan can do only:
* CVE scan, that verifies if all security updates are installed
* "Standard profile" scan, which is 5 or 6 rules

Expected results:
Atomic scan scans containers and images for any profile from SCAP Security Guide or customized profile and displays a report.

Additional info:
The scanning itself is already implemented upstream in Atomic https://github.com/projectatomic/atomic/pull/1027.

Note You need to log in before you can comment on or make changes to this bug.