commoncriteria / commoncriteria/fileencryption
APP -> MDF FDP requirements
Nobody has claimed this yet.
- Dominant language
- Makefile
- Stars
- 2
- Forks
- 3
- PR merge metrics
- No merged PRs in 30d
Description
For the MDF base scenario, the FDP_DEC_EXT and FDP_NET_EXT requirements do not make sense. Since the TSF in this case is handled as part of the MDF as a whole, it already has access to these services as a whole (since they are managed as part of the MDF).
FDP_DAR_EXT.1 is not quite so clear in the translation. I would probably create an MDF-specific SFR in the FE PPM that would be something like FDP_DAR_EXT.3 (called that because of the numbering in the MDF) that would detail FE for the PPM specifically. It would need to state something about selecting the sensitive data (though the term probably needs to be different since sensitive data is already being used as a term in the MDF).
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the MDF base scenario requirements FDP_DEC_EXT, FDP_NET_EXT, and FDP_DAR_EXT.1 alongside the FE PPM translation. Done means deciding which requirements apply and defining an MDF-specific FDP_DAR_EXT.3 requirement with clear terminology for selecting the relevant data.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100