Question 10
At Orchard Biotech, an infrastructure review by the laboratory network group is evaluating remote researcher access across a laboratory hybrid network while testing an alternate WAN provider (FT-D-12-01). The review finds that two remote teams need different posture standards but share an overly permissive endpoint profile. Any correction must respect this operating requirement: sensitive lab assets remain inaccessible to untrusted endpoints. Which ongoing control most directly reduces the chance of this issue returning?
Explanation
Correct Answer
This preventive control directly targets recurrence: Audit profile assignment after identity-group changes; make it a repeatable part of Orchard Biotech's change assurance (FT-D-12-01). It sustains the corrective action, separate and assign profiles according to documented user and device requirements, and must preserve the requirement that sensitive lab assets remain inaccessible to untrusted endpoints.
Incorrect Answers
The source case reports that two remote teams need different posture standards but share an overly permissive endpoint profile. That ongoing review concerns: Retest posture policy on client and operating-system updates; include explicit primary and alternate path tests. The governing risk here is: Audit profile assignment after identity-group changes; schedule a recorded review after topology changes. Maintain “Audit profile assignment after identity-group changes; schedule a recorded review after topology changes” as the case-specific check.
The source case reports that two remote teams need different posture standards but share an overly permissive endpoint profile. “Set DEM baselines before regional rollout and review anomalies; use a measured acceptance threshold where relevant” maintains another technical control: Set DEM baselines before regional rollout and review anomalies; use a measured acceptance threshold where relevant. It does not directly prevent this case’s specific recurrence, for which “Audit profile assignment after identity-group changes; schedule a recorded review after topology changes” addresses: Audit profile assignment after identity-group changes; schedule a recorded review after topology changes.
The source case reports that two remote teams need different posture standards but share an overly permissive endpoint profile. That ongoing review concerns: Maintain separate test cases for private TCP and UDP use cases; include explicit primary and alternate path tests. The governing risk here is: Audit profile assignment after identity-group changes; schedule a recorded review after topology changes. Maintain “Audit profile assignment after identity-group changes; schedule a recorded review after topology changes” as the case-specific check.