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/scm-configuration

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

SCM best practices: avoid auto-merge rules

Avoid the use of auto-merge rules in SCM platforms such as GitLab, GitHub, or Bitbucket, as this can allow untrusted or potentially malicious code to be deployed directly to production without sufficient review.

SCM best practices: require pull request reviews

Require pull requests to be reviewed before merging and ensure this review step cannot be bypassed to prevent untrusted code from reaching production.

SCM best practices: use protected branches

Leverage protected branches in SCM platforms to add additional controls and safeguards around critical branches.

SCM best practices: require signed commits

Require commits to be signed before they can be merged to ensure code authenticity and integrity.

SCM best practices: manage external contributions

Carefully weigh the risk against the benefits of allowing ephemeral contributors. Limit the number and permissions of external contributions when possible.

SCM best practices: enable MFA

Enable multi-factor authentication (MFA) where available on SCM platforms to protect against account compromise.

SCM best practices: manage user permissions carefully

Avoid assigning default permissions for users and roles with access to SCM assets. Carefully manage and minimize permissions.

SCM best practices: restrict repository forking

Restrict the ability to fork private or internal repositories to prevent unauthorized copies of sensitive code.

SCM best practices: limit repository visibility changes

Limit the option to change repository visibility to public to prevent accidental exposure of private code.

Give your agent this brain