datasheetAug 2026
CyberSafe Platform — Individual, CyberLink, Enterprise
One-pager of what each plan covers, what is scoped separately, and how onboarding works.
Threat Research · Documentation
Documentation for teams
who have to operate it.
Datasheets you can attach to a pack, plus onboarding and day-2 notes as they publish. Start with platform, assessment, and IR retainer one-pagers.
What you'll find
Reference first, fluff never
Documentation here is the operational companion to Advisories, Insights, and Guides. Published references start with datasheets — platform coverage, assessments, pentests, IR retainers, and GRC. Runbooks expand as platform onboarding ships; we do not pad this desk with fake titles.
Expect precise language, version notes, and clear ownership of who maintains each article. If something is not published yet, we say so rather than pad with placeholders dressed as live titles.
- Cloud
- Traffic
- Contain
Published references
Datasheets are the first published docs. Runbooks expand as platform onboarding ships.
datasheet
datasheetAug 2026
Cybersecurity assessment — engagement datasheet
Scope options, deliverables, and typical timeline for a posture assessment.
datasheetAug 2026
Incident response retainer — datasheet
What a retainer buys before 02:00: command, forensics path, and recovery support.
datasheetAug 2026
Penetration testing — engagement datasheet
External, assumed-breach, and web/API options. Evidence and a 90-day ladder — not a scanner export.
datasheetAug 2026
GRC & vCISO — engagement datasheet
Policy, risk register, control mapping, and board packs that match the controls you actually run.
Capabilities
Documentation categories
What operators ask for first.
Getting started
Account, environment, and engagement kickoff — what to prepare before day one.
01
Integrations
Cloud, identity, SIEM, ticketing, and endpoint connectors — scopes and prerequisites.
02
Operations
Day-2 runbooks: alerts, access, reporting cadence, and escalation paths.
03
Support & SLAs
How to open issues, what to include, and expected response windows by plan.
04
Process
How we keep docs trustworthy
Documentation is a control surface — stale pages are a risk.
- 01
Owner
Every page has a named maintainer and last-reviewed date.
- 02
Scope
Applies to which product, plan, or engagement type — no ambiguity.
- 03
Steps
Commands, UI paths, and expected outcomes tested against current build.
- 04
Failures
Common errors and what “success” looks like before you close the ticket.
- 05
Revise
Docs update with releases; deprecated paths are marked, not ghosted.
At a glance
Who documentation is for
Primary readers
- Administrators configuring CyberSafe and connected systems
- SOC and IT staff using monitoring and response workflows
- Implementers integrating APIs and data sources
- Client project leads onboarding their organization
What we avoid
- Marketing copy dressed as technical reference
- Undocumented screenshots with no version stamp
- Fake article titles implying content that is not published
- Guides that skip verification or rollback steps
Capabilities
How to use this desk
Start with the job you have today.
Implementing
Start with Getting started and Integrations for your stack.
01
Operating
Use Operations runbooks and Support paths for steady-state work.
02
Learning context
Pair docs with Security Guides and Insights when you need procedure or judgment.
03
Threat landscape
The surface does not sit still.
Cloud estates, identities, vendors, and employee devices shift every week. A once-a-year assessment is a snapshot. CyberSafe treats the attack surface as a live model — continuously scanned, ranked by business consequence, and tied to the work of closing what actually matters.
- Internet-facing services, identity paths, and cloud defaults mapped as one surface
- Automated probing tropes — phishing, credential stuffing, unpatched CVEs — ranked by impact
- A continuous scan model so new exposure is seen before it becomes an incident
Scanning · Cloud360° surface
Need a doc that is not published yet?
Tell us which integration or workflow you are blocked on. We'll prioritize documentation as it ships — or walk you through the configuration in a working session.
Request documentation help