Available in: Projects for the application security scan workflow described here. Its findings inform release decisions for Sites. Account, Workspace, Chat, and Agent access controls remain separate from application scanning.
Security work combines application design, controlled access, safe configuration, and verification. A scan can identify particular problems, but it does not replace application authorization or establish that every workflow is secure.
Review the current revision
Open Security in a Project with source on a branch. If you see Security not set up, choose Add security, then Save. Choose Scan now and open the completed scan to check its revision, coverage, and findings. For a request tracker, ask the Project to review the record-view route’s ownership check. Verify with two authorized test accounts that each can open its own example record and that one cannot read the other’s. Record the result separately from the scan findings.
Review scan coverage
Use the Project's security workflow to inspect the scan state, findings, and the checks that actually ran. Read coverage alongside the result.
| Result | Action |
|---|---|
| Canceled | Treat the interrupted scan as incomplete. |
| Failed | Review the failure before relying on the scan. |
| Findings | Review severity, affected code, and the proposed correction. |
| Limited coverage | Identify what was not checked before relying on the result. |
| Not applicable | Confirm the check does not apply to this application. |
| Passed | Review the covered checks and verify important application behavior. |
An earlier scan does not establish the state of later source changes. Recheck the relevant revision before relying on it for a release.
Protect the application's boundaries
- Enforce user and record permissions in application code.
- Keep secrets on trusted server-side paths.
- Limit external account permissions to the work required.
- Separate development and production data and credentials.
- Validate inputs and uploaded content.
Platform visitor access and an application's own login can both apply. A person who can visit a Site does not thereby gain source editing or Site management authority.
Verify a correction
Reproduce the finding safely, apply a focused fix, and repeat the relevant checks. Preserve evidence of what was tested and any remaining coverage gap. Security findings and publish-blocking state should be reviewed in the actual workflow before release.
See Testing for behavioral checks and Permissions for Workspace, resource, and credential controls.
Example: protect request records
A portal can appear correct while allowing one user to request another user’s record directly. Check authorization on the server-side read and update paths, not only whether the interface hides an edit button.
Review scan findings for the inspected revision, then verify the allowed and denied workflows. See Testing and Permissions.
Keep the review scoped
For a new upload feature, identify its input validation, object access, and server-side credential paths. Review the relevant scan findings and check an allowed upload plus a denied read in development. Storage explains the object lifecycle; Site access covers the separate visitor boundary.