Control vendor and contractor access to critical systems
Energy and water utilities run lean IT teams and are essential entities under NIS2. Adcyma keeps staff, vendor, and contractor access under control across Microsoft Entra ID and on-prem Active Directory.
What this looks like day to day
Utilities depend on external people: maintenance contractors, consultants for the billing system, technicians from equipment suppliers. Each one needs an account quickly, and each account tends to stay long after the job is done.
Most utilities are municipally owned but run their own IT, usually a hybrid of on-prem Active Directory and Microsoft Entra ID, with a team of a few people. NIS2 classifies energy and water as essential entities, which makes control over exactly this access mandatory.
- Contractor accounts created for a maintenance window are still active years later
- Nobody can quickly list which external people can reach operational systems
- On-prem AD for operations, Entra ID for the office, both managed by hand
- NIS2 supervision asks for evidence a small team has no time to assemble
The short version
How Adcyma solves this
Adcyma ties every account, internal or external, to an owner and an end date, and applies the same rules across both directories.
External accounts with end dates
Vendors and contractors get accounts that expire with the assignment. Extending is an explicit decision with an owner.
See lifecycle managementHybrid AD and Entra ID
One rule set covers the office side and the operational side, so nothing is managed twice or forgotten once.
How hybrid support worksEvidence for NIS2
Access reviews and logs answer the question of who can reach what, with evidence ready to show a supervisor.
See governance featuresHow you get there
Connect both directories
Connect Microsoft Entra ID and on-prem Active Directory so office and operations are in one view.
Find the external accounts
See every vendor and contractor account, who owns it, and when it was last used.
Give them owners and end dates
Existing external accounts get an owner and an expiry. New ones get both from the start.
Let reviews keep it tight
Scheduled reviews put external access in front of the people who know whether it is still needed.
What changes
Common questions
We are municipally owned. Does that change anything?
No. You run your own directory and your own IT, and Adcyma connects to that. Ownership does not matter, the directories do.
Does Adcyma reach into OT or SCADA systems?
Adcyma manages identities and access in Microsoft Entra ID and on-prem Active Directory. Where operational systems authenticate against AD, controlling those accounts and groups covers the access path to them.
How does this map to NIS2?
Energy and water are essential entities under NIS2, and access control with evidence is part of the requirements. Automated offboarding, expiring external accounts, and reviews cover the identity part.
Can we start with just the contractor problem?
Yes. A common first step is putting end dates and owners on external accounts, then extending the same automation to your own staff.
More solutions
Public Sector
For the companies and units inside a municipality: access that follows moves, and temporary accounts that close on time.
Schools & Education
Handle the start of term without weeks of account work, on a small IT team.
Tech & SaaS
Get control of access across all the tools your teams picked, with SOC 2 evidence as a byproduct.
See every external account you have
Start a free 14-day trial and connect your Entra ID tenant. No credit card, no consultants.