trust-center

To generate a public security trust page from scan data, this tool reads your latest scan results and produces a standalone index.html file displaying framework scores, security policies, and infrastructure overview.

The best way to deploy a security trust page to S3, Vercel, Netlify, or GitHub Pages is by using the deployment targets configured in the shasta.config.json file, which tailors the standalone output for your chosen hosting provider.

A trust page turns compliance results into an auditable artifact by converting complex scan data into a shareable, public-facing HTML dashboard that reflects your current security posture for stakeholder review.

Yes, you need a latest scan available in the database to publish a security trust page, as the tool reads current scan data to reflect your existing security and compliance posture.

Yes, you can customize branding and organization details on a generated security trust page by configuring the organization details and hosting options in the optional shasta.config.json file.

If your security trust page is not working, ensure a latest scan is available in the database and that your shasta.config.json file is correctly configured, as the tool requires this data to generate the page.