commoncriteria / commoncriteria/fileencryption
APP -> MDF FPT requirements
Nobody has claimed this yet.
- Dominant language
- Makefile
- Stars
- 2
- Forks
- 3
- PR merge metrics
- No merged PRs in 30d
Description
FPT_API_EXT.1 is not needed in the MDF scenario
FPT_AEX_EXT.1 -> FPT_AEX_EXT.* as part of the system, the MDF requirements should satisfy these app requirements
FPT_TUD_EXT.1 -> FPT_TUD_EXT.1 since this is part of the MDF, I would assume it is updated as part of the system, and not as an app, so it should be able to be satisfied by this requirement
FPT_TUD_EXT.2 -> I would expect this to not be needed since the update should be as part of the OS
FPT_LIB_EXT.1 -> I would expect this to go away since as part of the MDF, any libraries here should be considered under the control of the MDF OEM and as such not be third-party.
FPT_IDV_EXT.1 -> FPT_TUD_EXT.1.1 - I would expect this to be covered here since it would be part of the system, it could either be handled by the main OS version or by some separate version number (depending on the vendor)
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
Review the APP and MDF requirement definitions referenced in the issue, including FPT_API_EXT.1, FPT_AEX_EXT.*, FPT_TUD_EXT.1/.2, FPT_LIB_EXT.1, and FPT_IDV_EXT.1. Determine which APP requirements are covered, unnecessary, or need revised mappings in the File Encryption Protection Profile; completion requires an agreed requirements update.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation, security
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100