Skip to content

Reference to file encryption #8

@jfisherbah

Description

@jfisherbah

FMT_RVW_EXT.1 app note says: "If the file or part of the file is encrypted, the TOE will have to reject the file or decrypt it so that the user can review the data."

FDP_RIP_EXT.1 app note says: "If the file or part of the file is encrypted, the TOE will have to reject the file or decrypt it so that the tool and the user can review the hidden data."

These are the only places that reference encryption/decryption in the PP-Module. If we want to discuss cryptographic functionality, we should integrate requirements for it in more detail. For example, is it necessary to reference the PP-Module for File Encryption? Or would it be sufficient just to reference the relevant App PP SFRs? Either way we should consider adding a second use case for optional decryption functionality in the introductory section, and then figure out whether additional FCS SFRs need to be referenced, either from what's already in the App PP, the FE module, or to define new (impl-dep?) SFRs for this functionality if supported by a conformant TOE.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions