Skip to content

Latest commit

 

History

History
 
 

scap

Folders and files

NameName
Last commit message
Last commit date

parent directory

..
 
 
 
 
 
 
 
 

README

Caveats!

  • Twistlock has been installed with SCAP enabled via the twistlock.cfg or the twistlock_console.yaml file.
  • Only supported for the scanning of centos, fedora and redhat based images.
  • Only failed test results will be reported (passed tests and test results scheduled for the v2.5 release).

Running it

  • When installing Twistlock enable SCAP support. Within the twistlock.cfg set SCAP_ENABLED=true or via the API install within the twistlock_console.yaml file set the name: SCAP_ENABLED to true
  • In the Twistlock Console go to Manage > System > SCAP > click Add DataStream and select the SCAP datastream (e.g. passwd_perm_high.xml)
  • Go to Defend > Compliance > Policy select either an existing policy or click new compliance rule. Scroll down to compliance check id 4000 (note: custom compliance checks will start at ID 4000). Set the failed result Action accordingly (ignore, alert or block).
  • To trigger a scan of images within a registry go to Monitor > Vulnerabilities > Registry and click scan.

Sample SCAP Datastreams

  • CCE-3566-7 - File permissions for /etc/passwd should be set correctly (644) - passwd_perm_high.xml
  • CCE-3495-9 - The /etc/passwd file should be owned by the appropriate group (root) - passwd_group.xml
  • CCE-3958-6 - The /etc/passwd file should be owned by the appropriate user (root) - passwd_owner.xml

References