[PATCH 0/4] support for alternate titles

Gary Gapinski gapinski at nasa.gov
Tue Sep 4 17:55:35 UTC 2012


On 09/04/2012 01:01 PM, Jeffrey Blank wrote:
> DISA FSO. And I tried to make it clear that it is very problematic with
> regard to their stated strategy (as well as our strategy of reducing
> duplication).  But this is within the bounds of the project's
> flexibility, and is done in a way that later convergence would still be
> easy.

This appears to enable alternate titles for assembled benchmarks in
different venues.

It is highly likely that any DISA FSO titleing will not be appropriate
for all other venues.

Thus, the <title> for a <Rule> (and likely <Group>s and <Profile>s,
possible <Value>s) becomes a 1-n attribute of such, and each instance
will need a domain-specific (e.g., DISA FSO) unique identifier that may
apply to things other than titles (<Rule> ids, descriptions, warnings,
rationales, etc).

ACK.

I would like at some later time to discuss a syntax for benchmark
fragments, an XML Schema or other suitable schema for such, inclusive of
such issues like variant titles. This would foster more rigor of
maintenance of individual fragments.


More information about the scap-security-guide mailing list