Network Penetration
Testing

Network penetration testing (also called network VAPT or infrastructure pen testing) is a structured assessment where certified experts simulate real attacker techniques against your network — external perimeter, internal segments, Active Directory, wireless, and remote-access — to find exploitable weaknesses before an attacker does. Goes beyond vulnerability scanning to include manual exploitation, lateral movement, and privilege escalation chains.

Most enterprises need both. External validates what an unauthenticated attacker on the internet can do — perimeter is the obvious target. Internal simulates assumed-breach scenarios — what happens once an attacker has phishing-grade access. Combined coverage matches the way real intrusions actually unfold and is what RBI / SEBI / CERT-In annual audits expect.

Configurable per engagement. Zero-knowledge external mirrors a real adversary with no prior info. Assumed-breach grey-box gives us a low-privilege internal foothold and tests "given we got in, how far can we move" — a much more useful question for most enterprise threat models. We typically recommend a combination across an engagement.

Yes — with controls. We have OT-aware auditors, run passive-only by default in production OT, and require explicit authorisation before any active probe. Segmentation validation between IT and OT is a core service for our manufacturing and utilities customers.

External-only: typically 5–8 business days. Internal + AD: 7–12 days depending on environment size. External + internal + AD + wireless: 12–18 days. Lemon enforces daily progress tracking with a status update each working day.

Yes. The RBI Directions, 2026 require vulnerability assessment every six months and penetration testing every 12 months of critical information systems and / or those in the DMZ with a customer interface — expressly including network components (paras 150–151). SEBI CSCRF and the CERT-In annual audit both require network VAPT for regulated entities, and PCI DSS v4.0 Requirement 11.4 mandates internal and external network testing at least annually. Security Brigade has been CERT-In empanelled since 2008.

No, by design. We default to non-disruptive techniques in production. Anything DoS-class, fuzzing, or actively destructive is opt-in only with explicit authorisation and out-of-band escalation paths agreed in writing during scoping. Lemon logs every probe so you have a full audit trail.

Yes — reports include infrastructure-specific remediation (firewall rule examples, GPO settings, IAM policies, segmentation diagrams) plus an open call with your network team to walk through fixes. Retest rounds confirm closure.