Similar to the old issue #5, this is a case where an application focused requirement is bundled in with system software requirements.
To preserve numbering, this could become FPT_TUD_EXT.6.1, except this would be mandatory, so it probably means making this .3.1, and moving everything else up one (i.e. 3=>4, 4=>5, 5=>6).
There isn't anything wrong with this requirement, just that it doesn't really match everything else since it is a completely different layer and doesn't really have anything to do with the core components of the device.
Similar to the old issue #5, this is a case where an application focused requirement is bundled in with system software requirements.
To preserve numbering, this could become FPT_TUD_EXT.6.1, except this would be mandatory, so it probably means making this .3.1, and moving everything else up one (i.e. 3=>4, 4=>5, 5=>6).
There isn't anything wrong with this requirement, just that it doesn't really match everything else since it is a completely different layer and doesn't really have anything to do with the core components of the device.