This security policy describes how SprintAudit handles security incidents, manages vulnerabilities, and maintains controls to protect users and their data. SprintAudit is built entirely on Atlassian Forge — a secure, serverless platform managed by Atlassian.
Key principle: SprintAudit has no external servers, no external databases, and no data storage outside Atlassian infrastructure. All security controls are either inherited from Atlassian Forge or applied at the code level within the app.
1. Security Incident Response
In the event of a security incident affecting SprintAudit, we follow this response process:
- Detection — Security issues may be reported by users, discovered via Atlassian's EcoScanner, or identified during development review.
- Triage — Reported issues are assessed within 2 business days to determine severity and impact.
- Containment — For critical issues, a hotfix is deployed to production within 24 hours. For severe issues, within 7 days.
- Notification — Affected users and Atlassian are notified per the Atlassian Vulnerability Notification guidelines.
- Post-incident review — Root cause is documented and preventive measures implemented.
To report a security issue, please email: security@adarshini.co.in
We aim to acknowledge all security reports within 2 business days.
We aim to acknowledge all security reports within 2 business days.
2. Vulnerability Management
We take a proactive approach to identifying and remediating vulnerabilities:
- Dependency scanning — npm dependencies are scanned using
npm auditbefore every production deployment. Critical and high severity vulnerabilities are resolved before release. - Atlassian EcoScanner — All app versions submitted to the Atlassian Marketplace are automatically scanned by Atlassian's EcoScanner for authorization bypasses, insecure API usage, and other Forge-specific vulnerabilities.
- Code review — All changes are reviewed before deployment to ensure correct use of
api.asUser()(notapi.asApp()) for all Jira API calls, ensuring proper user-level authorization. - Bug fix SLA — We follow Atlassian's Marketplace Security Bug Fix Policy: P1 Critical within 5 days, P2 Severe within 30 days, P3/P4 within 90 days.
3. Access Control
- All Jira API calls are made using
api.asUser()— the app only accesses data the installing user has permission to view. - SprintAudit requests only the minimum Jira permissions required: read access to boards, sprints, issues, and project data. No write permissions are requested.
- Source code is stored in a private repository with MFA-protected access.
- Production deployments require authenticated Forge CLI access with MFA.
4. Data Protection
- SprintAudit stores no End-User Data outside Atlassian infrastructure.
- The only data stored is user configuration preferences (e.g. story points field selection, done statuses) in Atlassian Forge Storage — a key-value store scoped per app, per Atlassian site, encrypted at rest and in transit by Atlassian.
- No personal data (names, emails, account IDs) is stored or processed by SprintAudit.
- All data access uses HTTPS — enforced by Atlassian Forge's runtime environment.
5. Monitoring & Logging
- SprintAudit operates as a serverless Forge app — Atlassian manages the underlying infrastructure monitoring and logging.
- No sensitive data (credentials, tokens, personal information) is logged by the app.
- Atlassian Forge provides built-in audit logging for app invocations accessible via the Forge developer console.
- We monitor the Atlassian Marketplace Security (AMS) dashboard for any vulnerability reports flagged by EcoScanner.
6. Development Security Practices
- OWASP Top 10 guidelines are reviewed and applied during development.
- MFA is enforced on all development accounts including GitHub and Atlassian developer console.
- Dependencies are kept up to date and reviewed for known CVEs before each release.
- Security testing is performed before each production deployment.
7. Compliance
| Standard | Status |
|---|---|
| Atlassian Marketplace Security Requirements | ✅ Compliant |
| Atlassian EcoScanner | ✅ All vulnerabilities patched |
| GDPR | ✅ No personal data processed or stored |
| CCPA | ✅ Not applicable — no personal data collected |
| SOC 2 / ISO 27001 | Not applicable — inherited from Atlassian Forge infrastructure |
8. Security Contact
For security concerns, vulnerability reports, or incident notifications:
- Email: security@adarshini.co.in
- Response time: Within 2 business days
- Escalation: Critical issues escalated to Atlassian per their Security Incident Management Guidelines