Seeded demo · auth off · no application database · GitLab SoT / GitHub twin · not an ATO

How-to guides

Pick the task you need. Each guide links to the page where you do it.

Start here

Connect the platform once, then scan anything before it enters the enclave.

Connect GitLab and Rancher

First time setup, or when a page says GitLab or Rancher is not configured.

  1. Open Provision instances from the sidebar.
  2. In Connections, enter the GitLab URL, an access token, and the project that runs the pipelines. Add the Rancher URL, token, and Harvester cluster if you will provision VMs.
  3. Select Save. Values are encrypted on the app server and are never written to Git.
  4. Select Run self-test. It confirms each connection and that the browser database loads from this app, with no internet access.

You get: The status changes from Demo mode to armed, and scans, deploys, and provisioning run for real.

  • Values already set as server environment variables are used when no value is saved in the UI.
  • If the self-test reports the browser database failed, the app is not serving its bundled SQL runtime. Redeploy the full build output.
Open Provision instances

Scan an open-source package

Before a developer pulls an npm, PyPI, Maven, Go, Cargo, NuGet, or RubyGems dependency.

  1. Open Scan and choose Package.
  2. Pick the ecosystem, then type the package name and the exact version.
  3. Select Run scan.
  4. Review the advisories and the provisional ICD 203 SCRM threat evaluation.
  5. Download the ICD 203 output for the package record, or select Add to ledger.

You get: A threat evaluation in ICD 203 format, with a confidence level and its sources. Ledger entries keep the download, so you can find it again under Software evaluation.

  • A version with no published advisories is not proof it is safe. The confidence level says how much the evaluation can support.
Scan a package

Scan a container image

Before an image is promoted or used as a base for a workload.

  1. Open Scan and choose Container.
  2. Enter the Chainguard image reference, for example cgr.dev/chainguard/static.
  3. Select Verify.
  4. Read the proof chain from top to bottom: signature, SLSA build provenance, then the SBOM.

You get: Each link is checked against the Sigstore trust root bundled with the app, so verification also works on a closed network.

  • If any link in the chain is broken, the image fails. Do not use it, even when the other links pass.
Scan a container

Scan software on a base image

Before installed software (not a library) is approved for use on an IT baseline image.

  1. Open Scan and choose Software.
  2. Pick the IT baseline image to install on.
  3. Describe the software: its name, version, and where the installer comes from.
  4. Select Install and scan. A GitLab runner records the image, installs the software, records it again, then runs the STIG SCAP scan.
  5. Keep the page open to follow the pipeline. The report appears when the scan finishes.
  6. Review the results: SCAP failures by CAT level, and every service, local user account, registry key, and package the install added or changed.

You get: A pass or block decision. Results and artifacts are saved to the approved-software project in GitLab, and that project is created if it does not exist.

  • A CAT I failure blocks approval.
  • New local accounts and services are flagged for review. Justify or remove each one before approval.
  • For a report.json from an earlier run, use Import report, then Save to GitLab.
Scan software

Build & deploy

Turn approved software into something developers can run.

Package a deployment

A team needs approved software layered on an IT baseline image.

  1. Open Software catalog and select the Package & Deploy tab.
  2. Choose the IT baseline image.
  3. Check the packages and binaries to add. Only approved ledger entries can be selected.
  4. Preview the generated Helm chart and install script.
  5. Download the chart as a .tgz, or provision a developer instance from it.

You get: A Helm chart built on the baseline, or a running instance for the developer.

Open Software catalog

Design and deploy a workload

You need several Kubernetes components wired together, such as a deployment, service, and ingress.

  1. Open Design & deploy. Manage lists your connected clusters and saved designs.
  2. On Design, start from the template or a blank canvas. Add components and connect them.
  3. Select a component to set values such as the image tag, then select Save.
  4. On Deploy, review the validation and dry-run results, then select Deploy.

You get: A GitLab mesh-deploy pipeline that renders the manifests and waits for a manual apply.

  • Validation errors block a deploy. Fix the components it names first.
Open Design & deploy

Provision a developer instance

A developer needs a VM built from a hardened base image.

  1. Complete Connect GitLab and Rancher first.
  2. In the portal, choose the image and size, then submit the request.
  3. Follow the request in the instance ledger on Provision instances.

You get: A Harvester VM requested through Rancher. Each request is recorded in the local instance ledger.

Open the request portal

Build a hardened base image

IT is publishing a new baseline image.

  1. Open Base images.
  2. Start a golden-image build. Packer builds the image and Ansible applies the STIG.
  3. Promote the image once its smoke test passes.

You get: A STIG-hardened image you can pick in software scans and deployment packages.

Open Base images

Prove compliance

Show an assessor where each claim comes from.

Show in-toto build proof

An assessor asks how you know a build was not tampered with.

  1. Open Supply chain.
  2. On Main builds, select a pipeline to see its signed layout and the link metadata for each step.
  3. To check files you were sent, use Verify and upload the layout and its links. Verification runs offline.

You get: A pass or fail result for each step, signed with the layout owner key.

Open Supply chain

Review Rev. 5 control narratives

You are moving an eMASS package from Rev. 4 to Rev. 5.

  1. Upload the eMASS export.
  2. Enter your reviewer name so each decision is attributed to you.
  3. Expand a control row to read its narrative, then select Approve or Request changes.
  4. Export the narrative text for the SSP, or the full CSV.

You get: Reviewed narratives in the house style, ready to paste into the SSP.

  • Export buttons stay disabled until there is something to export. Hover over one to see what it needs.
Open Rev. 5 migration

If something looks wrong

A tile says No telemetry instead of a color
Nothing has been measured yet, so it is not a pass. The tile names the artifact or scan it needs.
A page says GitLab is not configured
Save the GitLab connection under Provision instances, then run the self-test.
A button is greyed out
A prerequisite is missing, such as an empty register or no uploaded file. Hover over the button for the reason.
A page you need is not in the sidebar
Open More tools at the bottom of the sidebar. It opens on its own when you are on one of those pages.