ChangeSafe for Jira Security Policy
Security architecture, operating controls and responsible vulnerability reporting for ChangeSafe for Jira.
1. Security architecture
- Hosted on Atlassian Forge
- Read-only Jira analysis
- No external ChangeSafe customer-data database
- No external ChangeSafe application server for core functionality
- Designed without external customer-data egress
2. Least privilege
ChangeSafe requests only the Jira permissions required for supported functionality.
3. Authorization
Protected site-level and app-authorized analysis verifies the current user's appropriate Jira administrative permission before protected app-context reads are allowed.
4. Read-only model
ChangeSafe does not request Jira configuration write permissions and does not perform Jira configuration changes.
5. Credentials
ChangeSafe does not require Atlassian passwords, customer Personal Access Tokens, customer API tokens, shared secrets or third-party service credentials.
6. Dependency security
Production dependencies are reviewed using automated software-composition and dependency-vulnerability analysis as part of the release process, and are updated through controlled testing.
7. Application security
- User-controlled identifiers are constrained and validated.
- Unsupported planned actions are rejected.
- Arbitrary external URLs or scripts are not executed as part of normal ChangeSafe functionality.
- Atlassian Forge platform security controls are used.
8. Logging
ChangeSafe is designed to avoid intentionally placing credentials, API tokens, passwords or unnecessary Jira customer content into application logs. Atlassian Forge may create technical operational logs.
9. Vulnerability reporting
Email security.changesafe@tennexdigital.com with the subject ChangeSafe Security. Include an issue description, reproduction steps, the affected feature, expected and actual behavior, and non-sensitive supporting evidence.
Never send passwords, API tokens, Personal Access Tokens, authentication codes, recovery codes or unnecessary customer data.
10. Security response
Tennex Digital will review reports, assess severity, investigate valid findings, prioritize remediation according to impact and applicable Atlassian Marketplace security requirements, and notify Atlassian or customers when required by applicable incident or vulnerability requirements.
11. Compliance
ChangeSafe currently does not claim independent certifications such as ISO 27001, SOC 2, PCI DSS, HIPAA, FedRAMP or similar certifications.
12. Scope
This Security Policy covers ChangeSafe for Jira. It does not cover Atlassian's own infrastructure or unrelated third-party applications.