Security Policy
Ivars Apps • Last updated: April 6, 2026
This Security Policy describes how Ivars Apps (Luis Ivars Unipessoal Lda) secures its Atlassian Marketplace applications and related systems. This policy applies to all apps published by Ivars Apps, including Project Intelligence Hub for Jira and Stakeholder View for Jira.
1. Platform Security
All Ivars Apps applications are built exclusively on Atlassian Forge, which provides:
- Sandboxed execution environment — app code runs in isolated containers managed by Atlassian
- No external servers — all processing occurs within Atlassian infrastructure
- Encrypted data at rest — Forge Storage (KVS) is encrypted by Atlassian
- Encrypted data in transit — all communication occurs over HTTPS/TLS
- Automatic scaling and availability managed by Atlassian
2. Authentication & Authorization
- Apps use
api.asUser() for user-context operations, ensuring actions respect the user's Jira permissions
- Apps use
api.asApp() for server-side operations (e.g., public views), with minimum required scopes
- No user credentials, passwords, or API tokens are collected, stored, or processed
- Web triggers validate access tokens on every request before serving any data
- Magic link tokens are randomly generated, revocable, and support configurable expiry dates
3. Data Protection
- Apps request only the minimum Forge scopes necessary for functionality (principle of least privilege)
- No end-user data is transmitted to external servers or third parties
- No personal data is stored beyond minimal app configuration (project settings, token metadata)
- All dynamic values rendered in HTML output are escaped to prevent cross-site scripting (XSS)
- No user input is passed to JQL queries or API calls without proper escaping via Forge route template literals
4. Vulnerability Management
- Dependencies are regularly reviewed using
npm audit for known vulnerabilities
- Forge CLI lint checks (
forge lint) are run before every deployment to detect security issues
- Third-party libraries are kept to a minimum and pinned to specific versions
- We monitor Atlassian's security advisories and update our apps accordingly
5. Incident Response
In the event of a security incident affecting our apps:
- We will investigate and assess the impact within 24 hours of becoming aware
- Critical security patches will be deployed within 72 hours
- Affected customers and Atlassian will be notified promptly following Atlassian's Incident Notification guidelines
- Post-incident reviews will be conducted to prevent recurrence
6. Secure Development Practices
- Source code is stored in private GitHub repositories with access controls
- Multi-factor authentication (MFA) is enabled on all development accounts (GitHub, Atlassian)
- Code is reviewed before deployment to production
- Development, staging, and production environments are separated using Forge's environment system
- We follow Atlassian's security requirements for cloud apps
7. Workstation Security
- Development workstations use full disk encryption
- Endpoint protection (antivirus) is active on all development machines
- Operating systems and development tools are kept up to date with security patches
- Strong password policies are enforced
8. Logging & Monitoring
- Apps do not log sensitive end-user data (PII, credentials, tokens)
- Forge platform provides built-in monitoring and error tracking
- Application errors are monitored via Forge runtime logs
9. Reporting Security Issues
If you discover a security vulnerability in any Ivars Apps product, please report it to:
We will acknowledge receipt within 48 hours and provide an initial assessment within 5 business days. We appreciate responsible disclosure and will work with reporters to address issues promptly.
10. Policy Updates
This Security Policy is reviewed and updated periodically. Changes will be reflected by updating the "Last updated" date at the top of this page.