|
| 1 | +# Organization Policy |
| 2 | + |
| 3 | +This is the enterprise-level Claude Code configuration that applies to all users |
| 4 | +in the organization. Settings here have the highest priority in the memory hierarchy. |
| 5 | + |
| 6 | +> **Note**: This file should be placed in the system-wide location: |
| 7 | +> - **macOS**: `/Library/Application Support/ClaudeCode/CLAUDE.md` |
| 8 | +> - **Linux**: `/etc/claude-code/CLAUDE.md` |
| 9 | +> - **Windows**: `C:\Program Files\ClaudeCode\CLAUDE.md` |
| 10 | +
|
| 11 | +## Security Requirements |
| 12 | + |
| 13 | +### Code Security |
| 14 | +- All commits must be signed with GPG keys |
| 15 | +- No secrets, API keys, or credentials in source code |
| 16 | +- Use environment variables or secret management tools for sensitive data |
| 17 | +- Required: security review for authentication-related changes |
| 18 | + |
| 19 | +### Access Control |
| 20 | +- Follow principle of least privilege |
| 21 | +- Document all permission requirements |
| 22 | +- Regular access audits required |
| 23 | + |
| 24 | +## Compliance |
| 25 | + |
| 26 | +### Data Handling |
| 27 | +- Follow organization's data classification policy |
| 28 | +- GDPR compliance for personal data |
| 29 | +- Audit logging for sensitive operations |
| 30 | +- Data retention policies must be followed |
| 31 | + |
| 32 | +### Documentation |
| 33 | +- All public APIs must be documented |
| 34 | +- Security-relevant decisions require ADR (Architecture Decision Records) |
| 35 | +- Change logs must be maintained |
| 36 | + |
| 37 | +## Approved Tools and Libraries |
| 38 | + |
| 39 | +### Package Management |
| 40 | +- Use only approved package registries |
| 41 | +- All dependencies must pass security scanning |
| 42 | +- Version pinning required for production dependencies |
| 43 | + |
| 44 | +### Container Images |
| 45 | +- Docker images must be from approved registry |
| 46 | +- Base images must be scanned and approved |
| 47 | +- No `latest` tags in production |
| 48 | + |
| 49 | +## Code Standards |
| 50 | + |
| 51 | +### Quality Gates |
| 52 | +- All code must pass linting before merge |
| 53 | +- Test coverage minimum: 80% |
| 54 | +- No high/critical security vulnerabilities |
| 55 | + |
| 56 | +### Review Requirements |
| 57 | +- All changes require code review |
| 58 | +- Security-sensitive changes require security team approval |
| 59 | +- Breaking changes require architecture review |
| 60 | + |
| 61 | +## Communication |
| 62 | + |
| 63 | +### Language Policy |
| 64 | +- Code comments: English |
| 65 | +- Documentation: English |
| 66 | +- Commit messages: English |
| 67 | + |
| 68 | +## Version Control |
| 69 | + |
| 70 | +### Branch Protection |
| 71 | +- Main branch is protected |
| 72 | +- Force push is prohibited |
| 73 | +- Squash merge preferred |
| 74 | + |
| 75 | +### Commit Standards |
| 76 | +- Conventional commits format required |
| 77 | +- Reference issue/ticket in commits |
| 78 | +- Sign-off required |
| 79 | + |
| 80 | +--- |
| 81 | + |
| 82 | +*This is a template. Customize according to your organization's policies.* |
| 83 | +*Last updated: 2026-01-22* |
0 commit comments