Question 300
At Bluehaven Telecom, an infrastructure review by the carrier access engineering group is evaluating customer support tool reachability across a metropolitan customer service network after an audit of cloud access (FT-E-10-02). The review finds that a user reports that web access was blocked and the SOC cannot match the endpoint event to the security policy verdict. Any correction must respect this operating requirement: service management data cannot cross tenant boundaries. Which corrective approach best resolves the observed issue while meeting the operating constraint?
Explanation
Correct Answer
The observed problem is that a user reports that web access was blocked and the SOC cannot match the endpoint event to the security policy verdict. Correlate endpoint identity and FortiSASE PoP traffic or security logs by timestamp and session as part of Bluehaven Telecom's customer support tool reachability update (FT-E-10-02), while enforcing the constraint that service management data cannot cross tenant boundaries. A successful implementation must be checked rather than assumed: In a controlled a metropolitan customer service network acceptance test, The case record links the user event to its relevant cloud policy decision; the outcome is recorded under Bluehaven Telecom's rollout (FT-E-10-02). The technical reason is that Cross-layer correlation is necessary when client and inspection evidence reside in different systems.
Incorrect Answers
The source case reports that a user reports that web access was blocked and the SOC cannot match the endpoint event to the security policy verdict. This option would change the control governed by: Logging usefulness depends on retention integrity and restricted reader permissions. That does not resolve the present failure, where correlate endpoint identity and FortiSASE PoP traffic or security logs by timestamp and session as part of Bluehaven Telecom's customer support tool reachability update (FT-E-10-02), while enforcing the constraint that service management data cannot cross tenant boundaries. The applicable response is “Correlate endpoint identity and FortiSASE PoP traffic or security logs by timestamp and session; confirm the dependent routing state”.
The source case reports that a user reports that web access was blocked and the SOC cannot match the endpoint event to the security policy verdict. The offered alternative is useful for: Inspect the applicable user or endpoint event records alongside traffic logs as part of Northpoint Health's clinic and telehealth connectivity update (FT-E-08-01), while enforcing the constraint that patient-service networks remain isolated from visitor access. In this case the decisive mechanism is: Correlate endpoint identity and FortiSASE PoP traffic or security logs by timestamp and session as part of Bluehaven Telecom's customer support tool reachability update (FT-E-10-02), while enforcing the constraint that service management data cannot cross tenant boundaries. The specific action is “Correlate endpoint identity and FortiSASE PoP traffic or security logs by timestamp and session; confirm the dependent routing state”.
The source case reports that a user reports that web access was blocked and the SOC cannot match the endpoint event to the security policy verdict. “Inspect IPsec negotiation logs peer reachability and expected identity or proposals; confirm the dependent routing state” addresses the technical dependency: IPsec failures can occur before routing or application policy is relevant. The reported problem instead follows: Correlate endpoint identity and FortiSASE PoP traffic or security logs by timestamp and session as part of Bluehaven Telecom's customer support tool reachability update (FT-E-10-02), while enforcing the constraint that service management data cannot cross tenant boundaries. The more direct correction is “Correlate endpoint identity and FortiSASE PoP traffic or security logs by timestamp and session; confirm the dependent routing state”.