Typical logs are also essential for a non-repudiation policy to be successful. Currently, we store logs for:

1. Platform logging system: Our platform stores a historical status of projects, findings, vulnerabilities, and other critical components. Changes made to these components are always tied to a user and a date. The historical status never expires. These logs cannot be modified.
   
2. Platform error tracking system: Our platform provides real-time logging of errors that occur in its production environments. It is especially useful for quickly detecting new errors and hacking attempts. These logs never expire and cannot be modified.
   
3. Redundant data centers: These store comprehensive logs of all our infrastructure components. Logs here never expire and cannot be modified.
   
4. DevSecOps execution: Whenever a client's CI pipeline runs DevSecOps, logs containing information such as who ran it, vulnerability status, and other relevant data are uploaded to our data centers. This allows us to always know the current status of our client's DevSecOps service. These logs never expire and cannot be modified.
   
5. IAM authentication: Our IAM stores logs of user login attempts, accessed applications, and possible threats. Logs here expire after seven days and cannot be modified.
   
6. Collaboration systems activity: Our collaboration systems, such as email, calendar, etc., store comprehensive talent activity logs, spam, phishing and malware emails, suspicious login attempts, and other potential threats. Talent activity logs never expire. Other security logs expire after 30 days. These logs cannot be modified.
   
7. CI job logs: All our CI pipelines provide a full record of who triggered them, when, and the console output. These logs never expire and cannot be modified.
   

Requirements

1. 075. Record exceptional events in logs
   
2. 079. Record exact occurrence time of events
   
3. 080. Prevent log modification
   
4. 376. Register severity level
   
5. 377. Store logs based on valid regulation