🛡️ Security Information

Sprint Scope Guard Security Boundary

Vendor: Neural Void | Platform: Atlassian Cloud Ecosystem | Last Updated: September 2026

This page explains the data flow and security controls for Sprint Scope Guard & Agile JQL Pro.

1. Application data flow

Sprint Scope Guard is a Jira Cloud Forge app. It uses the Jira and Forge storage permissions declared in its manifest to provide the current-sprint scope audit and authorized scope actions.

  • Forge storage: App state is stored through Forge-hosted storage. Atlassian documents its hosted-storage lifecycle, including retention after uninstall and recovery conditions, in its storage reference.
  • Optional manual webhook test: A project administrator may configure and test an approved Slack or Microsoft Teams endpoint. This outbound request is limited by the manifest allowlist; the app has no automatic threshold notifications.
  • Data residency: Forge documents hosted-storage residency behavior in its data-residency documentation.

2. Scope-action and webhook controls

Sprint Scope Guard applies these controls:

  • Scope actions: Sensitive actions are server-side and verify project access and issue/project binding before a scope change.
  • Webhook validation: The URL filter requires HTTPS, rejects embedded credentials, and rejects localhost, private/internal, loopback, link-local, metadata, and other non-public address forms.
  • Declared destinations: Forge allowlists only hooks.slack.com and *.webhook.office.com for this backend egress.

3. Marketplace availability

The Marketplace listing is under review. Availability and current pricing are published through Atlassian Marketplace.

4. Security reporting

Report suspected vulnerabilities through the contacts below. Start with the error code, approximate time and reproduction steps. Redact unrelated Jira content and never include passwords, API tokens or webhook URLs. Operational diagnostics use Atlassian Forge logs; platform metadata can identify the installation site, so these logs are not anonymous. Access follows the customer's log-sharing settings and the applicable Atlassian cloud offering.

5. Responsible Disclosure & Security Contact

We welcome responsible security reports from researchers, partners, and customers. If you believe you have discovered a vulnerability, please contact us immediately:

Security Contact: security@neural-void.com
Primary Operations: support@neural-void.com
Developer & Verification: vladimir.evseev.pro@gmail.com
Scope: Include the affected product, Jira site context, reproduction steps, and any relevant non-sensitive evidence.