Atlassian Forge runtime
Atlassian provides the underlying Forge platform. LTS remains responsible for application design, requested scopes, application logic, secure development and dependencies.
Security
Security starts with the product boundary.
LT Census Connect and LT Census Discovery do not inherit the same infrastructure responsibilities. Review them separately before applying family-level controls.
Load-bearing distinction
Two products. Two runtimes.
Connect runs inside Atlassian Forge. Discovery runs on infrastructure LTS operates outside Atlassian.
Trust boundaries
Responsibility follows the runtime.
A universal statement that assigns all Census infrastructure to Atlassian would be false for LT Census Discovery.
LTS operated infrastructure
LT Census Discovery operates outside Atlassian. LTS therefore owns responsibilities for the infrastructure it operates as well as the application layer.
Shared principles, applied per product.
Family-level language is useful only after the runtime, source access and operator have been identified.
Two trust boundaries
Connect runs on Atlassian Forge. Discovery runs on LTS operated infrastructure outside Atlassian.
Product-specific access
Each product documents the source access needed for its own capability and runtime.
Scoped access
Collection is limited to the accounts, projects, organisations or environments selected for that product.
Auditable execution
Every run records what Census attempted, what it found and what was synchronised.
Product detail belongs in assurance evidence.
Exact permissions, data handling, retention and operational controls require product-specific evidence. This page states the confirmed boundary without inventing missing assurance detail.
LT Census
Evaluate each product on its real boundary.
Tell us whether you are assessing Connect inside Atlassian Forge or Discovery on LTS operated infrastructure.