commoncriteria / commoncriteria/transforms

alternate introductory text and subsections for Module SARs

Open
#54 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
XSLT
Stars
1
Forks
4
PR merge metrics
No merged PRs in 30d

Description

The current schema for populating the SARs section of a module appears to be the tag. However, if that is the correct tag to use, it does not appear to be having any effect. i.e. it can be used in the input.xml without any schema errors but the freeform text inside is overridden by whatever goes in that section by default, and there doesn't appear to be any meaningful tags that work inside of it.

For a module, the expectation is that it can potentially define additional EAs for the SARs beyond what the Base-PP requires. If it doesn't do this, the default text that currently populates the SARs section is fine. But we want to have the option for adding something here.

For example, the STIP module defines specific guidance for AVA_VAN.1 because there are certain implementation flaws that are unique to STIP and need to be considered beyond what the NDcPP requires for that SAR. So we should be able to define a SARs section in a module that has its own intro text, one or more subsections for the SAR classes (ASE, ADV, AVA, etc.), freeform text underneath the subsection, and an . Guidance is needed as to whether this capability currently exists since it wasn't found in template materials. If it doesn't currently exist, it should be added as an optional capability for modules.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the tag in input.xml and inspect the template materials to determine how the SARs section is currently populated. Document whether module-specific introductory text, SAR-class subsections, freeform text, and an are supported; if not, define the optional module capability and verify it with a representative module such as STIP.

Written by the indexing model from the issue text.

Assessment

Tech stack
xml
Domain
tooling
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.