Your first security assessment

Before you begin

Have an agent configuration in JSON or YAML ready. Use a redacted copy: replace live credentials and tokens with placeholders before pasting or uploading it.

New to Foo Guard? Create an account, then open your Personal dashboard.

Run your first scan

1. Open the analyzer in your dashboard.
2. Paste your configuration or upload a JSON or YAML file.
3. Choose the rules you want to assess, or keep the default selection.
4. Run the analysis to see findings, a security score, and remediation guidance.

Rule packs group related checks to support your security goals. They do not certify compliance. See rule packs and coverage.

Understand the results

Each finding identifies a rule, a severity, and guidance for reducing the risk. Start with the highest-severity findings and inspect the relevant configuration.

• Findings explain which deterministic rules identified a risk.
• Score and grade summarize the assessed configuration.
• Remediation guidance helps you decide what to change.

Read understanding findings and security scores for details. Unassessed rules are not evidence that a check passed.

Make a change and scan again

Update the configuration in your source of truth, then scan the revised version. Compare the findings to confirm whether the relevant issue is resolved. Keep the original results for context.

Use the CLI

For repeatable scans, follow the CLI setup guide and configure an eligible personal API key or organization service key. With the CLI installed and authenticated, scan a local file:

fooguard scan ./agent.yaml --fail-on high

The command exits with 0 when the policy passes, 1 when the security policy fails, and 2 for an operational or configuration error. See CI/CD enforcement before using it as a build gate.

Bring your team along

Create a workspace to collaborate, then connect GitHub to bring checks into repository workflows. Use branch protection to require the checks your team relies on.