Security policy

Partner security policy for the Atlassian Marketplace apps published by Robert Venning: Link Health for Confluence and Code Blocks for Confluence. Last updated 17 September 2026.

Report a security issue: rvenning@proton.me with “Security” in the subject line.

Please name the app and describe the issue and how to reproduce it. Do not include customer data you are not authorised to share, and please do not disclose the issue publicly until it has been fixed.

How the apps are built

Security starts with keeping the attack surface small. Both apps are built on Atlassian Forge and run entirely on Atlassian’s infrastructure.

Security controls

AreaControl
Access control Only the publisher has access to the Atlassian developer and Marketplace accounts that can deploy or change the apps. Two-step verification is enforced on the Marketplace partner account. API tokens are personal, kept outside source code, and rotated if exposure is suspected.
Change control Every release is built from version-controlled source, tested against a fixture Confluence site in a development environment, and only then deployed to production with the Forge CLI. Scope or egress changes require Atlassian’s explicit administrator consent before they take effect on a customer site.
Data protection Data is processed only within Atlassian Forge, which provides encryption in transit and at rest. The apps log no page content or personal data; diagnostic logs record data structure only.
Dependencies Third-party packages are kept to Atlassian’s own Forge libraries. Dependencies are scanned with npm audit before each release and updated when a relevant vulnerability is published.
Monitoring Forge invocation logs and errors are reviewed through the Atlassian developer console, and Atlassian Marketplace security notifications are monitored.

Vulnerability management

  1. Reporting. Report to the address above. Reports forwarded by Atlassian, including through the Marketplace Security Bug Bounty program or the ecosystem service desk, are handled the same way.
  2. Acknowledgement. Reports are acknowledged within 2 business days.
  3. Triage. Each report is reproduced and rated for severity using CVSS, following Atlassian’s severity levels.
  4. Remediation. Fixes are released within the timeframes of Atlassian’s Marketplace Security Bug Fix Policy for the assigned severity. Critical issues are worked on immediately.
  5. Verification and disclosure. The fix is verified against the original report, the reporter is told when it is released, and customers are informed where action is needed on their side.

Security incidents

A security incident is any event that could affect the confidentiality, integrity or availability of customer data handled by the apps. If one is suspected:

  1. Contain. Stop the cause, for example by revoking credentials or deploying a fix or rollback. Forge allows an affected version to be replaced across all installations.
  2. Assess. Establish what happened, which customers and data are affected, and when.
  3. Notify. Notify Atlassian and affected customers without undue delay, with what is known, what has been done, and any action they should take.
  4. Recover and review. Confirm the issue is resolved, then record the root cause and the change made to prevent it happening again.