Frequently Asked Questions

Answers to common questions about our assessments, delivery, and working practices.

What types of assessments do you provide?

We offer penetration tests, red team exercises, wireless network assessments, web application and API testing, physical security reviews, social engineering campaigns, and security training. Each engagement is scoped to your goals and tailored to your environment.

How do you share findings during and after an engagement?

We provide an executive-ready PDF report and an interactive client portal with detailed findings, evidence, and remediation guidance. During active work, we publish daily dashboard updates so your team can follow progress in real time — you are never left waiting for a black-box report at the end.

How long does a typical engagement take?

Duration depends on scope and depth. An external network penetration test typically runs 3–5 business days. A combined external and internal assessment runs 7–14 business days. Web application assessments are usually 5–10 days depending on application complexity. We scope precisely during kickoff so you know the timeline before work begins.

Do you work with organizations that have no prior penetration testing history?

Absolutely. A first-time assessment is one of the most valuable investments an organization can make. We walk you through what to expect, help you define what's in scope, and deliver findings in a way that gives leadership clear priorities regardless of prior security program maturity.

What is the difference between a penetration test and a red team engagement?

A penetration test finds and documents as many exploitable vulnerabilities as possible within a defined scope and timeframe. A red team engagement simulates a specific adversary trying to achieve a defined objective — such as accessing sensitive data or reaching a critical system — without being detected. Red team exercises test your detection and response capability, not just the presence of vulnerabilities.

How do you protect sensitive data during an assessment?

We agree on data handling rules during scoping. Sensitive values such as passwords and hashes are masked in reports and portal views. Evidence is stored and transmitted using encrypted channels. We never retain client data beyond the agreed engagement period.

Can you work with our internal security team during the assessment?

Yes. We frequently coordinate with internal security, IT, and incident response teams. In some engagements your blue team is kept unaware to test detection; in others they participate. We align the coordination model to your goals during kickoff.

What should we prepare before an engagement begins?

You will need a point of contact, a list of in-scope systems or applications, any required credentials for authenticated testing, and availability for a kickoff call and final debrief. We send a simple pre-engagement checklist during scoping to guide this.

Do you provide remediation support after the assessment?

We deliver detailed remediation guidance with every finding. We also offer a retest window — when included in scope — to verify that fixes are genuinely effective rather than technically closed. Your team can track remediation status directly in the client portal.

How do you handle out-of-scope or unexpected critical findings?

If we discover something outside the agreed scope that poses an immediate risk — such as an actively exploited vulnerability — we notify your point of contact immediately, before continuing. We agree on the escalation process during kickoff so there are no surprises.

Are your assessments compliant with industry standards?

Our methodology follows PTES (Penetration Testing Execution Standard), OWASP Top 10 and API Security Top 10 for web and API work, MITRE ATT&CK for red team engagements, and NIST CSF for risk alignment in executive reporting. Findings are structured to support SOC 2, PCI-DSS, HIPAA, and similar compliance programs.

What is your approach to physical security assessments?

We evaluate entry controls, lock mechanisms, tailgating resistance, camera placement, badge procedures, and human factors at reception and access points. My Special Forces background informs how I assess physical perimeters — we look for how a real adversary would actually move through a facility, not just what a checklist suggests.