Skip to content

docs: add SECURITY.md with vulnerability reporting and safe usage guidelines#32

Merged
zakirkun merged 1 commit into
zakirkun:mainfrom
JULIANDEV21989:docs/add-security-policy
May 7, 2026
Merged

docs: add SECURITY.md with vulnerability reporting and safe usage guidelines#32
zakirkun merged 1 commit into
zakirkun:mainfrom
JULIANDEV21989:docs/add-security-policy

Conversation

@JULIANDEV21989

Copy link
Copy Markdown
Contributor

Summary

  • Adds SECURITY.md with responsible disclosure process and comprehensive safe usage guidelines
  • Covers the key security considerations identified during a full code audit of the repository

Sections Included

  • Reporting Vulnerabilities: GitHub Security Advisories preferred, 48h acknowledgment SLA
  • Environment Isolation: VM/container recommendation, dedicated venvs
  • API Key Management: Dedicated keys, spending limits, file permissions
  • OAST Callback: Configure your own out-of-band server
  • Plugin System: Security warnings, disabled by default
  • ML Model Files: Pickle deserialization risks
  • Scan Data Hygiene: Retention, cleanup after engagements
  • Legal Disclaimer: Authorization requirements
  • Known Security Considerations: Summary table of current status

Test plan

  • Verify SECURITY.md renders correctly on GitHub
  • Verify all links and references are accurate

🤖 Generated with Claude Code

…delines

Adds a comprehensive security policy covering:
- Responsible vulnerability disclosure process
- Environment isolation recommendations
- API key management best practices
- OAST callback configuration guidance
- Plugin system security warnings
- ML model pickle file risks
- Scan data hygiene and retention
- Legal disclaimer for authorized testing only
- Known security considerations table

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants