Effective Date: April 03, 2026
At Orbit A, security is integrated into every stage of our development process. Since our applications are built on the Atlassian Forge platform, we leverage Atlassian’s enterprise-grade security while maintaining strict internal practices.
1. Secure Development Practices
- Code Reviews: All code changes undergo peer review to identify potential security flaws before deployment.
- Static Analysis: We use automated tools (e.g.,
npm audit, ESLint) to scan for vulnerabilities in dependencies and ensure code quality.
- Least Privilege: Our app requests only the minimum necessary Scopes required to function within Jira.
2. Data Security & Encryption
- In-Transit: All data transmitted between your CI/CD environment and the Jira Webhook is encrypted using TLS 1.2+.
- At-Rest: We store data exclusively using Forge Storage API. Atlassian manages the underlying encryption at rest for this data.
- Isolation: Your data is logically isolated within your Atlassian tenant. Orbit A has no access to your Jira data or test results.
3. Access Control & Authentication
- Webhook Security: Access to the data ingestion endpoint is protected by a unique, cryptographically secure Security Token generated per installation.
- No PII: We do not collect or store Atlassian account passwords, personal API tokens, or PII.
4. Vulnerability Management & Incident Response
- Monitoring: We monitor our Forge logs for unusual patterns or errors that might indicate a security threat.
- Patching: We commit to patching any critical vulnerabilities within 48 hours of discovery.
- Incident Notification: In the event of a security incident, Orbit A will notify affected customers and Atlassian within 24 hours via official marketplace channels.
5. Contact Security
For security-related inquiries or to report a vulnerability, please contact: [email protected].