Most topics have a guide (*_guide.md) that walks through one task from
start to finish.
- The
paramifyCLI: every command, from manifests to uploads - Build a run manifest
- Give a fetcher its config and secrets
- Read an evidence envelope
- Follow one run through the framework
- How it runs: the four parts, the evidence envelope and the repo layout
- Evidence samples: what each fetcher collects, without a run
- Discovery fetchers: what a set of credentials can see in a platform
Platform setup. Most platforms have a guide for their credentials and permissions: AWS · Azure · GCP · Wiz · Datadog · Okta · CrowdStrike · Splunk · SentinelOne · KnowBe4 · GitHub · GitLab · Kubernetes · Rippling · Paramify · Checkov · ServiceNow · Jira · Oracle Cloud · FedRAMP Marketplace · Qualys · Sophos · Cornerstone
- Upload a run, and the API key and upload options
- Send scan reports to an assessment, and the scan-report uploader
- Run an inventory fetcher
- Sync fetcher scripts to Paramify
- Write a new evidence fetcher
- Port an existing fetcher
- Examine a fetcher against the contract
- Onboard a new platform
- Write an issue-report fetcher, and the Wiz pipeline guide
- Write a pipeline fetcher, and the pipeline fetchers design: inventory and scan fetchers that feed Paramify pipelines
- Write a comparator, the comparator reference, and the comparator design
- Fetcher to KSI mapping: which fetchers cover which KSIs, and the gaps
- Find the fetchers for a KSI