Industrial Defender ASMGetting started
How a Industrial Defender project goes from discovery to production, and what you need to get started.
How ASP Dijital delivers
We do not just resell the product: we deploy it and hand it over to your team.
-
Discover
In a workshop we clarify the current state, sources, goals and constraints, and choose the first use case together.
-
Pilot
We set up a Industrial Defender pilot with a limited scope and written success criteria, and judge the result against them.
- A single network segment or line: passive monitoring first, then active collection where suitable.
- Success criteria are written up front: inventory coverage, baseline configuration and the first report.
-
Roll out
We standardise the models, policies and templates from the pilot, integrate with surrounding systems and run a security review.
-
Enable and support
We train your team, hand over documentation and support you after go-live.
What you need to get started
None of it has to be ready: we complete it together in the discovery workshop.
- Scope: which plant, which Purdue levels, which network segments
- Existing network diagrams and known asset lists (they may be incomplete or outdated)
- Sensitive segments: places where active scanning must not happen
- Target frameworks (for example NERC CIP, IEC 62443, NIS2) and the tools to integrate (SIEM and so on)
Let’s take the first step with Industrial Defender together
Tell us where you are and what you want to achieve, and we will outline the right scope and pilot plan. Our team replies within 24 hours.