Cloud Security
Introduction
Smart Admin for Jira relies on enterprise-grade infrastructure. Built entirely on Atlassian Forge, our application inherits the exact same rigorous security boundaries, encryption models, and compute protections utilized natively by Atlassian Cloud.
Infrastructure & Compute
Unlike legacy Connect apps, Smart Admin eliminates external hosting risks entirely.
- check_circle Atlassian Hosted Compute: Our application runs natively inside the Atlassian Forge AWS infrastructure.
- check_circle Zero Egress: We do not process data outside Atlassian's secure boundaries or maintain proprietary compute instances.
Encryption & Protection
All data managed by the app benefits from industry-standard cryptographic protocols.
- encrypted Encryption at Rest: Temporary report data stored within Forge Storage is encrypted using AES-256 standard protocols.
- wifi_tethering Encryption in Transit: Traffic between the Jira API and the Forge compute layer occurs entirely over TLS 1.2+ internal connections natively provisioned by AWS.
Authentication Boundaries
The app uses explicit, strict declarative OAuth 2.0 scopes. It requests the absolute minimum read-and-modify permissions required to evaluate your schema.
no_accounts No Persistent Admin
We never manage external administrative service accounts. Authentication executes statelessly.
rule Strict Scopes
The application cannot read the internal content or attachments of your private Jira tickets.
Tenant Isolation & Data
-
domain_verification Strict Logical Separation
Relying on Forge's Tenant Context Service logic, all data is strictly segregated at a computational level. Operations performed dynamically on one client tenant cannot programmatically leak, access, or affect the architectural layout or metric evaluations of another.
-
auto_delete Automated Deactivation
Uninstalling Smart Admin automatically triggers cascading deletion flags across the Atlassian Forge storage layer. All cached report states are inherently scrubbed in alignment with global Data Destruction SLAs.
Incident Response
We execute a dedicated Incident Management Playbook modeled on Atlassian's Vendor Security Incident Response guidelines. In the event of ecosystem anomaly detection, we commit to immediate triage, transparent customer notification SLAs, and active root-cause eradication.
Compliance & Trust
We are tightly integrated into Atlassian's Marketplace Bug Bounty initiatives, incentivizing trusted security researchers to proactively uncover edge-case threats.
Because our app structure guarantees zero outbound data egress, it inherently supports seamless adoption within strictly regulated Jira environments (e.g., SOC2, ISO 27001).
Third-Party Subprocessors
We proudly maintain a heavily consolidated security footprint. We utilize no external marketing trackers, no remote telemetries, and zero third-party external sub-processors for any part of the algorithmic logic execution.
Vulnerability Management
-
bug_report SSDLC Adherence
All Smart Admin deployments operate under a rigorous Secure Software Development Life Cycle policy ensuring code passes strict peer-review formatting before public marketplace shipment.
-
radar Continuous Scanning
We deploy automated code analysis and comprehensive container vulnerability scanning throughout our CI/CD pipelines. This dedicated internal scanning runs continuously in parallel with Atlassian's native Ecoscanner protections to proactively identify and remediate threats.
Security Team Contact
Have further questions regarding compliance policies, Data Residency boundaries, or Forge architecture constraints? Reach out directly.