...
At Risk Radar, security is a top priority. We are committed to providing a secure and trustworthy risk assessment tool for Jira Cloud users. Our approach to security is built on industry best practices, Atlassian Forge security standards, and continuous improvements to ensure data integrity, confidentiality, and availability.
...
🚦 Detailed Security Information
1. Access Control and Authentication
All requests are processed through the Atlassian API. User authentication is provided via OAuth 2.0.
The application does not store passwords or user personal data.
Data access is determined by Jira role-based permissions (RBAC).
2. Data Storage and Processing
Risk data is stored in Jira Issue Properties (within the task).
No data is transferred outside Atlassian Cloud.
Optional feature to add comments for transparency.
3. Encryption and API Security
All connections are secured via HTTPS/TLS 1.2+.
The application uses Atlassian Forge Runtime, eliminating the need to store data in third-party databases.
4. Incident Management
Atlassian manages security infrastructure (DDoS, WAF, IAM).
Errors are logged in the Atlassian Dev Console.
5. Compliance with Atlassian Requirements
Risk Radar complies with Forge Security Guidelines.
Security policies are outlined in the Privacy Policy.
...
📌 Our Security Approach
We follow a multi-layered security model to protect customer data, ensure secure access, and mitigate security threats. Our security program is aligned with Atlassian Marketplace requirements and best practices for Forge apps.
...
While Risk Radar follows strict security measures, customers should also follow best practices to maintain security within their Jira Cloud environments:
✅ Control user access permissions to prevent unauthorized access.
✅ Keep Jira up to date with the latest security patches from Atlassian.
...
Contact & Security Reporting
If you identify a potential security vulnerability or have security concerns, please contact us at:
📧 Email: riskradarjira@gmail.com
...