Skip to content

APP -> MDF FPT requirements #49

@woodbe

Description

@woodbe

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)

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions