Offensive testing, compliance audit and 24×7 detection in one engagement: VAPT across network, application and cloud, control audits mapped to ISO 27001, SOC 2 and Indian regulator expectations, third-party risk assessment, and a Security Operations Center built on open source.
- VAPT across network, web, API, mobile and cloud configuration
- GRC audit against ISO 27001, SOC 2, PCI DSS, NIST CSF and the DPDP Act
- Third-party and supply-chain risk assessment with a scored register
- 24×7 SOC on Wazuh, Suricata and Zeek, with incident response retainers
How it fits together
Test it, audit it, then watch it around the clock
One engagement covers the three things usually bought separately: offensive testing, compliance audit and 24×7 detection.
Your environment
- Network and endpoints
- Web, API and mobile
- Cloud and third parties
Assess
- VAPTVulnerability assessment and penetration testing
- GRC auditISO 27001, SOC 2, PCI DSS, DPDP
- Third-party risk
24×7 SOC
- Wazuh
- Suricata
- Zeek
Response
- Triage and contain
- Notify
- Report and retest
What We Do
Six practices that are usually sold separately. Run together, a finding from a test becomes a control in the audit and a detection rule in the SOC.
Vulnerability Assessment & Penetration Testing
Authenticated and unauthenticated testing against the estate you actually run, scoped in writing before anything is touched.
Governance, Risk & Compliance
Control audits that produce the evidence an assessor asks for, and a risk register your board can actually read.
Third-Party Risk Management
Your suppliers' weaknesses become yours at audit time. TPRM makes that exposure explicit and tracked.
Security Operations Center
24×7 detection and triage on an open-source core, deployed on your infrastructure so telemetry never leaves the estate.
Attack Surface Management
Most breaches start on something nobody knew was exposed. ASM keeps the external picture current between tests.
OT & ICS Security
Plant networks cannot be patched on an IT schedule. Security there is segmentation, monitoring and discipline.
How an Assessment Runs
Six stages, fixed before we start. You know the scope, the rules of engagement and the deliverable date on day one.
Scope and authorise
Targets, exclusions, testing windows and emergency contacts agreed in writing. Nothing is touched without a signed authorisation, and out-of-hours windows are set where production risk demands it.
Discover and map
Passive reconnaissance and asset discovery build the real attack surface, which is almost always larger than the asset register says it is.
Test and exploit
Manual testing against the mapped surface; tooling assists but does not decide. Exploitation stops at proof, we demonstrate impact rather than pivoting further than the scope allows.
Report
Findings ranked by CVSS and by business impact, each with reproduction steps, evidence and a specific remediation. Separate executive and technical documents, because the two audiences need different things.
Remediate together
A working session with your engineers to sequence the fixes, and our hands on the tooling where you want them. Remediation advice is useless if it assumes a team you do not have.
Retest and attest
Closed findings are retested and a formal attestation issued, the document your customers and auditors actually ask for. Retesting within 90 days is included in the engagement.
Assessment Types at a Glance
What each engagement covers and how often it is usually run. Cadence is a starting point; regulated estates and public-facing products need more.
| Assessment | Typical cadence | What it covers |
|---|---|---|
| External network VAPT | Twice yearly | Internet-facing perimeter: exposed services, patch level, misconfiguration, credential exposure and the path from outside to inside. |
| Internal network VAPT | Annually | Assumed-breach testing from inside the LAN: lateral movement, privilege escalation, segmentation failures and domain compromise paths. |
| Web & API application | Per release | OWASP Top 10 and API Top 10, authentication and session handling, authorisation logic, injection and business-logic abuse. |
| Cloud configuration review | Quarterly | IAM policy, storage exposure, network security groups, logging coverage and key management across AWS, Azure and GCP. |
| Configuration & hardening audit | Annually | Servers, network devices and databases benchmarked against CIS baselines, with a prioritised hardening plan. |
| Phishing simulation | Quarterly | Targeted campaigns with per-department reporting, measured on report rate rather than click rate alone. |
| Red team simulation | Annually | Goal-based adversary simulation across people, process and technology, run against a defending SOC to test detection, not just prevention. |
Frameworks We Audit Against
We audit and prepare you against these standards. Certification itself is always issued by an accredited body, never by us.
ISO/IEC 27001:2022
Full Annex A control gap assessment, Statement of Applicability, risk treatment plan and internal audit ahead of your certification body's visit.
SOC 2 (Type I & II)
Trust Services Criteria readiness, control design review, and the evidence-collection routine that makes a Type II observation window survivable.
PCI DSS 4.0
Scope reduction first, then segmentation testing and control validation. The cheapest cardholder data environment is the smallest one.
RBI / SEBI / IRDAI
Cyber security framework alignment for regulated Indian entities, including VAPT evidence, audit trails and the reporting obligations each regulator sets.
DPDP Act 2023
Personal data mapping, consent and retention review, breach notification readiness and Data Principal rights handling.
NIST CSF 2.0
Govern, Identify, Protect, Detect, Respond and Recover scored as a maturity baseline, useful when no single certification is mandated.
Inside the SOC: What Happens When Something Fires
The runbook is written before go-live and rehearsed. An incident is not the moment to decide who calls whom.
Detect
Wazuh correlates host, network and cloud telemetry; Suricata and Zeek supply the wire view. Detection rules are tuned to your estate, because an untuned SIEM trains analysts to ignore it.
Triage
An analyst validates against the runbook and assigns severity. False positives are fed back into rule tuning the same week, so alert quality improves instead of decaying.
Contain
Host isolation, account disablement or firewall action under pre-agreed authority. What we may do without waking you is decided during onboarding, in writing.
Notify
You are called on the agreed path. Where CERT-In's directions apply, the six-hour reporting clock is tracked from detection and the submission drafted for your sign-off.
Eradicate and recover
Root cause established, persistence removed, and service restored from a known-good state. Recovery is verified rather than assumed.
Review
A written post-incident review within five working days: timeline, root cause, what detection missed, and the control and rule changes that close the gap.
The Security Stack
Open source wherever it is genuinely competitive, commercial where it is not. Every licence is stated, so nothing is presented as free when it is not.
Our SIEM and XDR core: host intrusion detection, file integrity monitoring, vulnerability detection and compliance mapping. Genuinely free at scale, which is why the SOC is built on it.
High-performance IDS/IPS on the wire, with tuned rulesets rather than the default firehose.
Network security monitoring that produces rich connection metadata, the record you want when reconstructing an incident weeks later.
Authenticated vulnerability scanning across the estate, scheduled and trended so remediation progress is visible rather than asserted.
Used where an auditor names it specifically, or where its plugin coverage beats OpenVAS for a given vendor appliance. Licensed per scanner.
The working tool for manual web and API testing. Licensed per tester; we do not pretend the community edition is equivalent.
Automated DAST wired into CI pipelines, catching regressions between the manual tests.
Exploit validation and proof of impact, kept strictly inside the agreed rules of engagement.
Cloud security posture assessment across AWS, Azure and GCP, mapped to CIS benchmarks and run on a schedule.
Container image, IaC and dependency scanning, shifted into the pipeline so findings land on developers rather than on auditors.
Threat intelligence sharing and IOC management, feeding indicators straight into detection rules.
Case management and observable analysis for the SOC. The community edition covers most estates; scale and support features are paid.
Endpoint visibility and digital forensics at speed, used during response to answer 'where else did this happen'.
Self-hosted phishing simulation, so campaign data and individual employee results stay inside your organisation.
What You Receive
Deliverables are fixed in the statement of work. If a document is not on this list for your engagement, it is because you did not ask for it, not because it costs extra.
| Deliverable | Format | When |
|---|---|---|
| Executive summary | PDF, 2–3 pages | With the main report. Written for a board: business risk, spend required, and what happens if nothing is done. |
| Technical findings report | PDF + CSV | With the main report. Every finding with CVSS v3.1 score, evidence, reproduction steps and a named remediation owner. |
| Evidence pack | Archive | With the main report. Raw output, screenshots and request/response captures, so a third party can verify our work. |
| Remediation plan | Spreadsheet | Within five working days. Findings sequenced by risk against effort, with realistic owners and dates. |
| Retest attestation | Signed PDF | After retest, within 90 days. The letter your customers and auditors ask for. |
| Risk register | Spreadsheet | Ongoing, for GRC engagements. Scored, owned and reviewed quarterly rather than written once and filed. |
| Monthly SOC report | Monthly, for SOC clients. Alert volume, true-positive rate, mean time to triage, and the rule changes made that month. |
Coverage at a Glance
What we do ourselves, and what we do with a partner
Testing, audit, SOC operations and incident response are delivered by our own team. CERT-In empanelled audit is delivered together with an empanelled partner and the certificate is issued in their name, we will introduce them before you commit. Certification against ISO 27001, SOC 2 or PCI DSS is likewise always issued by an accredited certification body or QSA, never by us: we prepare you for it and run the internal audit, which is a different service and priced as one.
Use Cases
A customer's security questionnaire has stalled the deal
A scoped VAPT and a retest attestation answer what procurement is actually asking, usually within three weeks.
The auditor arrives in six weeks
Gap assessment, evidence collection and an internal audit run first, so the external visit confirms readiness instead of discovering problems.
Nobody knows what is exposed to the internet
Attack surface discovery against your domains and ranges, returning an owned inventory and a ranked list of what to close first.
Alerts fire all night and nobody acts on them
Rule tuning and documented runbooks, then analyst triage on a rota, so alerts reach a human who knows what to do with them.
A supplier was breached and you need an answer today
Exposure assessed against that vendor's access and data, with a written position for your customers and your regulator.
The plant network and the office network are the same network
Segmentation designed to the Purdue model and delivered in stages, with passive monitoring where active scanning is unsafe.
Talk to an engineer about Cyber Security & GRC Audit
We start with your environment as it actually is: architecture, tooling, gaps, constraints and the outcomes the business is asking for.
Get in Touch