Differences between revisions 2 and 6 (spanning 4 versions)
Revision 2 as of 2015-08-18 10:09:50
Size: 876
Editor: FranklinPiat
Comment: Done: packaging openscap and scap-workbench
Revision 6 as of 2016-12-14 07:42:01
Size: 1402
Editor: ?PetterReinholdtsen
Comment: Mention sources for package CPE values.
Deletions are marked like this. Additions are marked like this.
Line 3: Line 3:
This page is a TODO/IDEAS list to implement a SCAP guide for Debian.
This page is a TODO/IDEAS list to implement a SCAP guide for Debian.  Debian automatically generates and publishes [[https://www.debian.org/security/oval/|OVAL information]] for use by SCAP.
Line 7: Line 6:
Line 8: Line 8:
 * What are Debian CPEs (platform, family?)  * What are Debian CPEs (platform, family?). Many CPEs can be found in the testing security SVN repostory, svn+ssh://svn.debian.org/svn/secure-testing, in the data/CPE/ directory. In addition, some source packages include the known CPEs for the package in debian/upstream/metadata).
Line 18: Line 18:
 * Define communication channels so contributors can follow and participate (IRC, mailing list, etc.)
Line 23: Line 24:
 * Fix the [[Bug:738199|broken]] OVAL information for Debian

Debian SCAP Guide

This page is a TODO/IDEAS list to implement a SCAP guide for Debian. Debian automatically generates and publishes OVAL information for use by SCAP.

TODO

  • Define the Profiles we want.
  • What are Debian CPEs (platform, family?). Many CPEs can be found in the testing security SVN repostory, svn+ssh://svn.debian.org/svn/secure-testing, in the data/CPE/ directory. In addition, some source packages include the known CPEs for the package in debian/upstream/metadata).

  • Define distribution we target (typically: testing then stable)
  • How to let our derivative fork easily?
  • How to cooperate with scap-security-guide
  • Test infrastructure?
  • Dashboard
    • Compare: our supported checks, upstream checks, and a wishlist.
    • Each SCAP probe should be tested, both in unstable and testing
    • Each Debian distribution should be evaluated, for each relevant profile.
  • Write docs
  • Define communication channels so contributors can follow and participate (IRC, mailing list, etc.)

Later...

  • Translating the SCAP guide
  • Support older distribution
  • provide framework so maintainers can provide probes in their packages
  • Fix the broken OVAL information for Debian

Done