Skip to content
sentrasec
Book a demo →

Quickstart

Install the CLI, scan a repository and read your first findings.

This guide takes you from nothing to a set of real findings. It needs a terminal and a repository.

Install the CLI

On macOS and Linux:

curl -fsSL https://cli.sentrasec.ai/install.sh | bash

On Windows, in PowerShell:

irm https://cli.sentrasec.ai/install.ps1 | iex

The installer places the sentrasec binary on your PATH. Confirm it is there:

sentrasec --version

Run a scan

Point it at a repository:

sentrasec scan .

That runs every scanner applicable to what it finds: source files trigger SAST and secrets detection, lockfiles trigger SCA, Terraform, Helm, Kubernetes, Dockerfile, CloudFormation and Bicep files trigger the IaC scanner. Results are deduplicated before they are reported.

Read the findings

Each finding reports what matched, where, and why it matters:

HIGH  SQL injection via string concatenation
      src/api/users.py:47
      CWE-89 · OWASP A03:2021

      User input from request.args reaches a query string
      without parameterisation.

      Remediation: use a parameterised query

To narrow what you see:

sentrasec scan . --severity high
sentrasec scan . --scanners sast,secrets

Connect a workspace

Authenticating connects the scan to an app in your workspace, so findings are triaged and kept:

sentrasec login
sentrasec scan .

The same scan now returns findings with a triage decision (remediate or defer) and the evidence behind it. Findings that need action get a remediation plan and a test plan, which your coding agent can pick up over MCP.

Add it to CI

The same binary runs in your pipeline. In GitHub Actions:

- name: Security scan
  run: |
    curl -fsSL https://cli.sentrasec.ai/install.sh | bash
    sentrasec scan . --format sarif > results.sarif
  env:
    SENTRASEC_TOKEN: ${{ secrets.SENTRASEC_TOKEN }}

Exit codes follow your severity threshold, so the build fails on what you define as blocking rather than on any finding at all. See CI/CD integration for the full setup.

Next steps

  • Core concepts: the model the rest of the documentation assumes.
  • Running scans: scanner selection, output formats and filtering.
  • MCP server: hand findings and remediation plans to your editor's coding agent.
Quickstart · Sentrasec