Skip to content

Commit

Permalink
Remove Caret char in SSCS (#1489)
Browse files Browse the repository at this point in the history
  • Loading branch information
jxdv authored Sep 12, 2024
1 parent dd779a4 commit 6ed5c2a
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion cheatsheets/Software_Supply_Chain_Security.md
Original file line number Diff line number Diff line change
Expand Up @@ -38,7 +38,7 @@ The practices described below are general techniques that can be used to mitigat

#### Implement Strong Access Control

Compromised accounts, particularly privileged ones, represents a significant threats to SSCs. Account takeover can allow an attacker can perform a variety of malicious acts including i^njecting code into legitimate dependencies, manipulating CI/CD pipeline execution, and replacing a benign artifact with a malicious one. Strong access control for build, development, version control, and similar environments is thus critical. Best practices include adhering to the basic security principles of least privileges and separation of duties, enforcing MFA, rotating credentials, and ensuring credentials are never stored or transmitted in clear text or committed to source control.
Compromised accounts, particularly privileged ones, represents a significant threats to SSCs. Account takeover can allow an attacker can perform a variety of malicious acts including injecting code into legitimate dependencies, manipulating CI/CD pipeline execution, and replacing a benign artifact with a malicious one. Strong access control for build, development, version control, and similar environments is thus critical. Best practices include adhering to the basic security principles of least privileges and separation of duties, enforcing MFA, rotating credentials, and ensuring credentials are never stored or transmitted in clear text or committed to source control.

#### Logging and Monitoring

Expand Down

0 comments on commit 6ed5c2a

Please sign in to comment.