

Frequently Asked QuestionsQ: Will discovery activities impact our production systems?
A: No. ARC.Discovery uses exclusively passive monitoring techniques that observe network traffic without any interaction with production devices or protocols.Q: How quickly can we see initial results?
A: Initial asset inventory appears within 24-48 hours, with comprehensive discovery typically complete within 2-3 weeks depending on network complexity.Q: What data do you need from our side?
A: Network architecture diagrams, VLAN configurations, and read-only access to network infrastructure for tap/span deployment. No credentials or device access required.

Key Questions AnsweredQ: How do you ensure scanning doesn't disrupt operations?
A: All active scanning occurs only during pre-approved maintenance windows with plant personnel present and immediate rollback capabilities tested and ready.Q: What's included in the remediation roadmap?
A: Prioritized action items with cost estimates, resource requirements, maintenance window alignment, and business impact analysis for each recommendation.Q: How often should assessments be repeated?
A: Annually for comprehensive reviews, with quarterly updates for high-risk environments or those undergoing significant infrastructure changes.




Safety and Methodology QuestionsQ: How do you ensure production systems aren't impacted?
A: All exploits are pre-validated in ARC.Lab digital twins. Production testing occurs only during maintenance windows with full plant operations oversight and immediate rollback capabilities.Q: What's the difference between red team and purple team testing?
A: Purple teaming combines offensive testing with defensive team collaboration, ensuring both sides learn and improve detection/response capabilities together.Q: How long does a typical penetration test take?
A: 4-6 weeks including planning, ARC.Lab validation, controlled production testing, and comprehensive reporting phases.

Exercise Structure and BenefitsQ: How realistic are the crisis scenarios?
A: Scenarios are based on actual threat intelligence and your specific environment, incorporating real attack techniques and operational constraints your organization faces.Q: How often should crisis exercises be conducted?
A: Quarterly tabletop exercises with annual full-scale simulations, increasing frequency based on threat level and regulatory requirements.Q: What teams should participate in exercises?
A: IT, OT, executive leadership, legal, communications, and any external partners involved in incident response procedures.