Red team vs. penetration test, what's the difference?
A penetration test enumerates and validates vulnerabilities within a defined scope. A red team is objective-driven and adversarial: it tests people, process, and technology together and measures whether a motivated attacker can reach your crown jewels without being caught. A red team includes the technical coverage of a pentest and goes further: active exploitation, social engineering, evasion, and full post-access operations.
What if you can't break in from the outside?
Real adversaries have unlimited time; an engagement doesn't. If a hardened perimeter won't crack inside the window, we pivot to an Assumed Breach, starting from inside as though access already happened, so you still get a full read on internal detection, lateral movement, and blast radius. We scope many red teams with this pairing from the start.
Is a red team safe to run against production?
Yes. Every engagement runs under strict rules of engagement, with deconfliction channels and OPSEC controls agreed up front. We emulate adversary impact without causing it, demonstrating access to crown jewels rather than damaging them.
Do you perform physical intrusion or on-site social engineering?
No, by design. Arcanum red teams focus on the digital and human attack surface: external compromise, phishing and social engineering, and full network operations, all conducted remotely. Physical intrusion, badge cloning, tailgating, facility access, is intentionally outside our scope, so you know exactly what the engagement covers.
How long does an engagement take?
It's scope-dependent, but full-scope red teams typically run several weeks to allow for realistic, low-and-slow operations. We size the timeline to your objectives, environment, and the level of stealth required.
Can you emulate a specific threat actor?
Yes. Threat-intelligence-led engagements emulate the TTPs of the actors most likely to target your sector, mapped to MITRE ATT&CK, so the exercise reflects a threat you'll realistically face.
.e4746d86.jpg)