List of awesome open-source developer security tools. Maintained by BoxyHQ, and heavily inspired by MVSP.
It includes security principles and controls relevant to popular compliance certifications (like ISO27001, SOC2, MVSP, etc.). Also check this list of popular compliance frameworks and certifications
Interested in the future of developer security? Join our Discord community to share and collaborate.
We’d love your feedback and contributions to this list. Please submit a GitHub issue or PR.
Business controls |
|||
---|---|---|---|
Control |
Description |
Compliance Controls |
Tools |
Vulnerability Reports |
|
|
|
Customer Testing |
|
|
|
External Testing |
Contract a security vendor to perform annual, comprehensive penetration tests on your systems |
|
|
Training |
Implement role-specific security training for your personnel that is relevant to their business function |
|
|
Compliance |
|
|
|
Incident Management |
|
|
|
Application Design Controls |
|||
Control |
Description |
Compliance Controls |
Tools |
Single Sign-On |
Implement single sign-on using modern and industry standard protocols |
|
|
Access Control |
|
|
|
HTTPS-Only |
|
|
|
Dependency Patching |
Apply security patches with a severity score of "medium" or higher, or ensure equivalent mitigations are available for all components of the application stack within one month of the patch release |
|
|
Logging |
Keep logs of:
Logs must include user ID, IP address, valid timestamp, type of action performed, and object of this action. Logs must be stored for at least 30 days, and should not contain sensitive data or payloads. |
|
|
Backup and Disaster Recovery |
|
|
|
Encryption |
Use available means of encryption to protect sensitive data in transit between systems and at rest in online data storages and backups |
|
|
Application Implementation Controls |
|||
Control |
Description |
Compliance controls |
Tools |
List of Sensitive Data |
Maintain a list of sensitive data types that the application is expected to process |
|
|
Data Flow Diagram |
Maintain an up-to-date diagram indicating how sensitive data reaches your systems and where it ends up being stored |
|
|
Vulnerability Prevention |
Train your developers and implement development guidelines to prevent at least the following vulnerabilities:
|
|
|
Infrastructure and Cloud Security |
Perform audits, continuous monitoring, hardening and forensics readiness for your infrastructure and cloud assets. |
|
|
Code Security |
|||
Control |
Description |
Compliance controls |
Tools |
Data Leakage Prevention |
Protect secrets from leaking into code, logs and unwanted systems. |
|
|
Zero Trust Principles |
Keep data encrypted from end-to-end and have no listening ports for malware/ransomeware to spread etc. |
|