Zero Network Egress
No permissions.external entries in manifest.yml. Atlassian's Forge network boundary blocks outbound traffic at the platform layer.
XXE Entity Rejection
Every XML parser (.iflw, PI/PO ICO, WSDL/XSD, and payload simulator) strictly rejects <!DOCTYPE and <!ENTITY> declarations before evaluation.
25 MB ZIP-Bomb Cap
Custom streaming PKZIP reader enforces a strict 25 MB uncompressed byte ceiling, 250-entry cap, CRC-32 verification, and path-traversal rejection.
Zero SAP Tenant Credentials
SpecSync operates on exported design-time bundles and CI commits—never requesting OAuth client secrets or admin access to live SAP production systems.
1. Atlassian Forge nodejs22.x Tenant Isolation
SpecSync v3.0 runs exclusively inside Atlassian's managed Forge serverless compute environment (app.runtime.name: nodejs22.x). Each invocation executes inside a per-tenant isolated micro-VM context scoped to your Atlassian cloudId:
- Strict Tenant Partitioning: Forge Encrypted App Storage keys are cryptographically isolated per Atlassian Cloud installation by the Forge runtime; cross-tenant reads are architecturally impossible.
- Thin-Client Browser Boundary: The Confluence Custom UI frontend communicates exclusively over
@forge/bridgeRPC calls within Atlassian's CSP-restricted iframe sandbox. - Zero Third-Party Parser Dependencies: SpecSync's PKZIP extractor, BPMN2/XML parser, Java UDF AST transpiler, and ADF builder are written in pure Node.js standard-library modules (
crypto,zlib,buffer), eliminating transitive open-source supply-chain attack surface beyond official@forge/apiand@forge/resolverSDKs.
2. Least-Privilege OAuth 2.0 Scopes
SpecSync v3.0 requests only four granular Atlassian platform scopes—never requesting user profile access, admin configuration permissions, or space-wide deletion rights:
| Forge Scope | Exact Justification |
|---|---|
storage:app |
Stores structural SHA-256 package fingerprints, evaluation quota counters, and optional HMAC webhook signing keys in Forge Encrypted Storage. |
read:page:confluence |
Reads the target Confluence page version number required by Confluence REST API v2 optimistic concurrency prior to updating a specification page. |
write:page:confluence |
Publishes validated Atlassian Document Format (ADF v1) integration specifications to user-designated Confluence pages. |
write:jira-work |
Creates structured Jira Cloud issues for breaking v1-to-v2 contract drift, PI/PO migration wave stories, and CAB release-gate blockers. |
3. Input Hardening, Webhook Authentication & Rate Limiting
- XML External Entity (XXE) & Billion-Laughs Defense: All XML inputs undergo pre-parse security screening that immediately aborts with
SecurityErrorif any DTD<!ENTITYor external system identifier is present. - Decompression Bomb & Zip-Slip Protection: Both standard PKZIP archives and Java/OSGi streaming Bit-3 (
0x0008) archives are bounded to a maximum of 250 entries and 25 MB cumulative uncompressed bytes, with..relative path segments rejected. - Constant-Time Webhook Verification: Incoming requests to
specsync-ci-webhookvalidatex-specsync-signatureusingcrypto.timingSafeEqualoverHMAC-SHA256digests. - Burst Rate Limiting: Built-in per-tenant rate limiting caps automated resolver bursts at 20 invocations per minute to protect tenant stability.
4. Vulnerability Disclosure & Security Contact
SyncForge Cloud Systems welcomes coordinated security disclosures and enterprise CISO security questionnaires. Contact our security engineering desk at support@syncforgecloud.com with subject line [SECURITY] SpecSync v3.0. Confirmed high-severity findings are triaged within 24 hours and patched via Atlassian Forge production rollouts.