All tutorials
You are reading the tutorials for Cordon 0.4 (0.4.1). Read this for 0.7, the current release.
Tutorials · Cordon 0.4.1

Cordon tutorials

17 tutorials covering the scanner as release 0.4.1 ships it: each a single use case to read, run and move on from, with 59 diagrams. Start with your first scan. Every page and section links to its source on GitHub at v0.4.1.

Start here

  1. 01Your first scaninstall, scan, read the output, exit codes2 diagrams
  2. 02How detection worksthe pipeline: sources → detectors → findings2 diagrams

By what you want to catch

  1. 03Malware & known vulnerabilitiesadvisory DB, typosquats, dependency confusion2 diagrams
  2. 04Reachability, cut noise without hiding anythingcut CVE noise without hiding anything2 diagrams
  3. 05Provenance & attestation, prove the sourceprove a package was built from its real source2 diagrams
  4. 06Secrets, credentials and exfiltration59 secret rules, 8 exfiltration rules, 47% of the pack6 diagrams
  5. 07CI/CD pipeline attacksattacks on the pipeline, across seven CI systems6 diagrams
  6. 08Containers, Kubernetes and infrastructure as codeDockerfile, compose, Kubernetes, Terraform5 diagrams

Running it for real

  1. 09The advisory databasekeep the intel fresh (OSV + signed bundle)2 diagrams
  2. 10CI & git hooksfail-on gates, SARIF, fail-closed pre-commit2 diagrams
  3. 11Air-gapped installsoffline bundles, deterministic scans3 diagrams
  4. 12Vetting a package before you install itanswer "should I install this?" before you do7 diagrams

Going deeper

  1. 13AST rules & capabilitieshow rules see through obfuscation ([ast-js])3 diagrams
  2. 14Config, policy & baselinesorg ceilings, adopt-incrementally3 diagrams
  3. 15Output formatstext | json | sarif | junit | markdown | github0 diagrams
  4. 16The sandbox -- running what you do not trustthe one component that executes, and its isolation6 diagrams
  5. 17Source, build systems, binaries and licencesbuild systems, binaries, licences, scan scope6 diagrams

The one thing to remember

Cordon READS. It never runs the code it is scanning, and it does not touch the network unless you pass --online. A scan is safe to point at hostile packages and safe to run in an air-gap.