Separates roles to secure log data integrity.

Separates roles to secure log data integrity.

• A. SoD in log management
• B. Data management governance
• C. Data classification policy
• D. Federation solutions

Answer: (A)

Separation of duties (SoD) applied to log management helps protect the integrity of log data by ensuring that no single person or process has the power to both influence and conceal log records. Logs are a record of what happened—authentication attempts, access events, and system actions—and their trustworthiness is essential for audits and incident response. By dividing roles—one team or process handles generation and collection, another handles storage and protection (often with append-only or tamper-evident storage), and a separate party reviews and verifies the logs—you reduce the risk that someone could alter or delete entries without detection. Implementations like append-only storage, cryptographic signing or hash chaining of log entries, time stamping, and strict access controls reinforce this separation and make tampering detectable. Other options touch on different aspects: data management governance is broader and not focused specifically on who can alter logs; data classification policy deals with labeling data by sensitivity; federation solutions relate to cross-domain authentication and trust, not log integrity through role separation.

Separation of duties (SoD) applied to log management helps protect the integrity of log data by ensuring that no single person or process has the power to both influence and conceal log records. Logs are a record of what happened—authentication attempts, access events, and system actions—and their trustworthiness is essential for audits and incident response. By dividing roles—one team or process handles generation and collection, another handles storage and protection (often with append-only or tamper-evident storage), and a separate party reviews and verifies the logs—you reduce the risk that someone could alter or delete entries without detection. Implementations like append-only storage, cryptographic signing or hash chaining of log entries, time stamping, and strict access controls reinforce this separation and make tampering detectable.

Other options touch on different aspects: data management governance is broader and not focused specifically on who can alter logs; data classification policy deals with labeling data by sensitivity; federation solutions relate to cross-domain authentication and trust, not log integrity through role separation.