Customizable Security Policies
Your organization's Security Policy starts from one of three presets: Essential, Balanced, or Comprehensive. Balanced is the default. Each preset sets an action (Block, Warn, Monitor, or Ignore) for every alert type, and a custom setting on any alert type overrides the preset.
This page covers the Security Policy page in the Socket dashboard. If your organization has migrated to Policies, see Baseline Presets instead.
Choose a preset
Pick the preset that matches how your team reviews dependencies:
- If you want malware and vulnerability coverage like a traditional software composition analysis (SCA) tool, choose Essential. It blocks known malware and warns on critical CVEs.
- If you also want developers warned about supply chain risks such as typosquats, protestware, and git or URL dependencies, choose Balanced. It blocks only known malware. Most teams start here.
- If your team vets new dependencies before adding them, choose Comprehensive. It also blocks critical CVEs, AI-detected potential malware, and git, GitHub, and HTTP dependencies.
Alert actions by preset
The following table lists the action each preset sets for each alert type. Alert types that aren't in the table are set to Ignore in all three presets, so you must enable them yourself.
| Alert type | Essential | Balanced (default) | Comprehensive |
|---|---|---|---|
| Known malware | Block | Block | Block |
| AI-detected potential malware | Warn | Warn | Block |
| Critical CVE | Warn | Warn | Block |
| High CVE | Monitor | Monitor | Warn |
| Medium CVE | Monitor | Monitor | Monitor |
| Low CVE | Monitor | Monitor | Monitor |
| License Policy Violation | Warn | Warn | Warn |
| Git dependency | Ignore | Warn | Block |
| GitHub dependency | Ignore | Warn | Block |
| HTTP dependency | Ignore | Warn | Block |
| Possible typosquat attack | Ignore | Warn | Warn |
| Protestware or potentially unwanted behavior | Ignore | Warn | Warn |
| Obfuscated code | Ignore | Warn | Warn |
| Deprecated | Ignore | Monitor | Warn |
| Shrinkwrap | Ignore | Monitor | Warn |
| Telemetry | Ignore | Monitor | Warn |
| Unpopular package | Ignore | Monitor | Warn |
| Unpublished package | Ignore | Monitor | Warn |
| Unstable ownership | Ignore | Monitor | Warn |
| AI-detected potential security risk | Ignore | Ignore | Monitor |
| Bad dependency semver | Ignore | Ignore | Monitor |
| Install scripts | Ignore | Ignore | Monitor |
| Manifest confusion | Ignore | Ignore | Monitor |
| Potential vulnerability | Ignore | Ignore | Monitor |
| Unmaintained | Ignore | Ignore | Monitor |
| Wildcard dependency | Ignore | Ignore | Monitor |
What each action does
Each action controls where an alert appears and whether it stops a change:
| Action | Shows in the dashboard | Developers see it | Blocks the change |
|---|---|---|---|
| Block | Yes | Yes | Yes |
| Warn | Yes | Yes | No |
| Monitor | Yes | No | No |
| Ignore | No | No | No |
Developers see Block and Warn alerts as GitHub pull request comments and CLI warnings. A Block alert also fails the Socket check on the pull request and makes the CLI exit with an error.
Change the preset or an alert's action
Change your organization's preset or the action for a single alert type on the Security Policy page:
- In the Socket dashboard, go to Settings → Security Policy.
- Select Essential, Balanced, or Comprehensive. Alert types set to Inherit switch to the new preset's action.
- To change one alert type, set its action to Block, Warn, Monitor, or Ignore. This custom setting stays in place when you switch presets. To follow the preset again, set the action back to Inherit.
- To discard every custom setting, select Remove Custom Settings. Every alert type returns to the preset's action.
- Check the alert list on the Security Policy page. Each alert type shows the action you chose.
Related topics
Updated about 6 hours ago