SMB Security Essentials
Comprehensive security assessment tailored for growing businesses with complex infrastructure.
In scope
- External/Internal network penetration test
- Web application assessment (1 application)
- Active Directory security review
- Cloud configuration review (AWS/Azure/GCP)
- Compliance gap analysis
You receive
- Detailed technical report
- Cloud security scorecard
- AD security metrics
- Web app vulnerability assessment
- 1-hour findings review
What's inside this engagement
Phase by phase.
How a security assessment engagement runs, what happens in each phase and what you see. Exact scope, tier and timeline are fixed in your proposal and SOW.
01Scoping
Systems, sites, stakeholders and the question the assessment must answer.
You see · Your objectives and constraints.
02Discovery & evidence
Documents, configurations and interviews, plus technical testing where the service includes it.
You see · Access and time with key people.
03Analysis
Findings rated by risk to your business, not by a generic score.
You see · A prioritized view of your risk.
04Report & debrief
Executive summary, findings and a remediation roadmap, walked through with your team.
You see · The report and the debrief.
Commercials
From first call to final report.
- 01
Scoping call
A practitioner, not a salesperson, walks through targets, constraints and what a good outcome looks like for you.
- 02
Proposal & rules of engagement
A fixed-scope proposal with tier, price and deliverables. Rules of engagement, contacts and out-of-bounds systems are agreed in writing.
- 03
Sign, then start
MSA and SOW are signed electronically and the deposit is paid. Only then does testing begin.
- 04
Execution
Testing runs to the agreed plan. Critical findings are escalated as they are found; you don't wait for the report.
- 05
Report & debrief
An executive summary plus technical findings with evidence, reproduction steps and fixes, walked through with your team.
- 06
Retest
Where the tier includes it, we verify your fixes and reissue the report, so auditors and customers see the issues closed.
Timelines are set per engagement in the SOW.
Related
Red Team Subscription
A standing offensive testing program in place of a once-a-year engagement. Each month our team runs a targeted assessment against an agreed part of your environment; each quarter a scenario-based attack tests how well your people and tooling detect and respond. The Premium tier adds two full red team engagements a year. Findings from every cycle feed one running improvement plan, so each round also checks whether the last round's fixes held. Targets, rules of engagement and testing windows are agreed at kickoff.
AI & Agentic Red Team
Offensive testing of LLMs and AI agents — prompt injection, jailbreaks, tool misuse, agent goal hijack, memory/context poisoning, model extraction, and agent identity abuse. Mapped to OWASP Top 10 for Agentic Applications, OWASP LLM Top 10, and MITRE ATLAS.
AI/ML Security Assessment
Expert evaluation of artificial intelligence and machine learning systems security, from model development to deployment. Our assessment identifies vulnerabilities in AI/ML infrastructure, examines risks of data poisoning, adversarial attacks, and model manipulation while providing guidance for securing these advanced technologies.
Research
Latest from the blog
ciso-strategy · Sep 24, 2026
Brinqa-PlexTrac and Cribl-Radiant Deals Signal CTEM and SOC Platforms Are Absorbing Point Tools
Thirty-three cybersecurity M&A deals in August 2026, led by Brinqa-PlexTrac and Cribl-Radiant Security, show exposure management and SOC platforms swallowing offensive-security and AI-native automation tools.
risk-management · Sep 23, 2026
Three Linux Kernel Flaws Hit CISA's KEV List: A CISO Triage Playbook
CISA added three actively exploited Linux kernel CVEs to its KEV catalog with a 72-hour federal remediation window. Here is a step-by-step triage order for CISOs.
incident-response · Sep 22, 2026
The Revolut Breach Is a Case Study in Confusing Authentication With Authorization
Revolut disclosed customer data to attackers who spoofed a government agency's email domain for five months. The root cause was not weak email security but a workflow that treated a valid domain as proof of a valid request.
Start an engagement