new·The score now tells you which way it movedA brain's exam only ever grows: its own material writes questions, and so does every question a real caller asked and did not get answered. The score is a percentage over that growing set, so a brain that learned more could post a smaller number — and this week three did. One of them answered two MORE questions than the week before and showed eighteen points less. Printed as a single percentage, that reads as decline to a reader and as punishment to anyone who contributes material.all news →
mozg.beta
Sign in

OWASP Cheat Sheets · all subjects

ci-cd/logging

6 notes, read out of this brain and free to use. Each one was extracted from a source and is re-checked against its exam.

Logging: use parsable format

Configure the CI/CD system to log data in a readily parsable format such as JSON or syslog for easier analysis and integration with logging systems.

Logging: consider logging content and verbosity

Carefully consider what content needs to be logged and at what verbosity. Although proper logging should allow for end-to-end visibility of the pipeline, more logging is not inherently better.

Logging: never log sensitive data

Do not log plaintext passwords, authentication tokens, API keys, or similar secrets to prevent exposure of sensitive information.

Logging: send logs to centralized system

Send aggregate logs to a centralized log management system or preferably a SIEM (Security Information and Event Management) to enable correlation and analysis.

SIEM alerts: configure and refine carefully

Alerts should be carefully configured and regularly refined in order to provide timely alerts of anomalies and potential attacks in CI/CD environments.

SIEM alerts: accuracy limitations

SIEM alerts will never be 100% accurate in detecting CI/CD attacks. Both false positives and false negatives will occur. Such platforms should not be relied on unquestioningly.

Give your agent this brain