Security Policy

Overview

This Security Policy describes the secure design and operational practices for PII Shield, a Jira Cloud PII detection and redaction app built on the Atlassian Forge platform.

Hosting & Infrastructure

PII Shield is built on the Atlassian Forge platform and runs entirely within Atlassian's infrastructure. There are no external servers, databases, or third-party backends hosted by Appcento. All compute resources are provided by Atlassian as part of the Forge runtime.

Data Access & Permissions

The App uses Atlassian's OAuth mechanism to access Jira data. Only the minimum required API scopes are requested:

Scope	Purpose
read:jira-work	Read issue content and metadata for PII detection scanning
write:jira-work	Redact PII in issues and comments by updating content with [REDACTED] placeholders
storage:app	Store detection findings, evidence bundles, and app configuration in Forge Key-Value Storage

These are the minimum scopes required for the App to function. No additional permissions are requested.

Data Storage & Processing

All data processing occurs within your Jira Cloud instance via Atlassian Forge:

• Encrypted storage: All data is stored in Forge Key-Value Storage, which is encrypted at rest by Atlassian as part of their infrastructure security.
• PII detection: Issue content is scanned for PII patterns using regex-based matching. Detected PII is immediately redacted with [REDACTED] placeholders.
• Evidence artifacts: Timestamped records with SHA-256 hashes are created for each detection, providing tamper-evident audit trails.
• No external storage: The App does not store any issue data, field values, or user information on external servers.

Network Security

The App makes no network calls to external third-party services.

• All API communication is with Jira's REST API through Forge's secure runtime and OAuth mechanism.
• Data in transit is encrypted via TLS as enforced by Atlassian's infrastructure.
• There is no egress from Atlassian's Forge runtime to external endpoints outside Atlassian unless explicitly added and approved in the app manifest.

Privacy Enhancing Technologies

PII Shield implements the following privacy enhancing technologies:

• Data masking/redaction: PII detected in Jira issues is immediately redacted and masked. Original values are never stored permanently.
• SHA-256 hashing: Used for tamper-evident audit trails. Hash chains provide integrity verification without exposing underlying data.
• Encrypted vault: Original PII values are encrypted (AES-256-GCM) in Forge Secure Storage for admin verification purposes only, with automatic deletion after 30 days.

Vulnerability Management

Appcento follows these vulnerability management practices:

• Dependency updates: Dependencies are reviewed and updated regularly to address known vulnerabilities.
• Automated scanning: npm audit (Software Composition Analysis) is run on every build as part of the CI/CD pipeline.
• Minimal footprint: The app has a minimal dependency footprint: only @forge/api, @forge/bridge, @forge/react, and @forge/ui-kit.
• Atlassian platform security: The App relies on Atlassian's platform security for underlying infrastructure, runtime patching, and vulnerability management.

Incident Response

In the event of a security incident or vulnerability discovery:

• Appcento will coordinate with affected customers and Atlassian as required.
• Notifications will be sent to impacted contacts via the support email channel within 48 hours of discovery.
• Patches and mitigations will be applied as quickly as possible through the Forge deployment pipeline.
• For security issues, contact: [email protected]

Compliance

PII Shield complies with the following standards and frameworks:

• Atlassian Marketplace compliance: The App has passed Atlassian's security review and listing requirements.
• Data residency: All data storage and processing uses Atlassian Forge infrastructure, which supports Atlassian's data residency program.
• Atlassian Trust Center: The App inherits Atlassian's platform-level security controls and certifications. Refer to:

• Atlassian Trust Center
• Atlassian Cloud Security Practices

Third-Party Services

The App does not use third-party analytics, monitoring, or telemetry services. No customer data is sent to external vendors.

Changes to This Policy

We may update this Security Policy from time to time. Any changes will be reflected by updating the "Effective Date" at the top of this document.

Contact

For security questions or to report a vulnerability, contact:

Email: [email protected]
Website: https://appcento.com

---