Follow the admin rights
Privileged Access
Assessment
We find where administrative privilege lives across your directories, cloud platforms, servers and vendor connections, how it is granted, and who watches its use. You learn which accounts would give an attacker control of the business, where standing admin access should become just in time, and which fixes cut the most risk.
Where privilege hides
Fewer admins,
watched more closely.
We measure privilege against the Microsoft enterprise access model, CIS Controls v8.1 Controls 5 and 6, and NIST SP 800-53 AC-6. BloodHound maps privilege paths in Active Directory and Entra ID. We interview admins about how they really work, then compare that with what the systems show.
What we examine
Directory admins
Count every route to Domain and Global Admin.
A privilege path graph showing every account, group and delegation that leads to directory control.
- Domain Admins, Enterprise Admins and nested groups enumerated.
- ACL and delegation paths mapped with BloodHound.
- Entra ID privileged roles and PIM settings reviewed.
Cloud admin roles
Find who can change your cloud at the top level.
Owners and administrators across AWS, Azure and Google Cloud, with standing rights that should be eligible only.
- Organization, subscription and project admin roles listed.
- Root and break glass accounts checked for protection and monitoring.
- Just in time access tools reviewed where they exist.
Service accounts
Look at the accounts no person logs into.
Service accounts with admin rights, old passwords, or interactive logon that should be blocked.
- Service account privilege and password age reviewed.
- Kerberoastable accounts with admin reach flagged.
- Group managed service accounts recommended where they fit.
Endpoints & servers
Check local admin rights across the fleet.
Where users and helpdesk staff hold local admin, and whether Windows LAPS keeps those passwords unique.
- Local administrator membership sampled across workstations and servers.
- Windows LAPS deployment and who can read its passwords reviewed.
- Linux sudo rules and root access checked.
PAM & monitoring
Test how privileged use is approved and watched.
Which admin actions are approved, recorded and alerted on, and which happen with no trace.
- PAM vault, session recording and checkout rules reviewed.
- Alerts on privileged logins and log coverage checked.
- Admin workstations and separate admin accounts examined.
Vendor access
See what outside parties can do with admin rights.
Every vendor and MSP path into your environment, with the privilege it carries and how it is controlled.
- Remote support tools and vendor VPN accounts inventoried.
- MSP admin roles and delegated admin relationships reviewed.
- Approval steps and time limits on vendor sessions checked.
Key benefits
Take standing admin rights off the table.
Nested groups, old delegations and forgotten service accounts create admins nobody approved. We find them, show the path each one takes to control, and tell you which to remove first.
We show where standing admin rights can move to just in time access through PIM or your PAM tool, so a stolen account carries far less power on an ordinary day.
Some privilege fixes break workflows. We rank changes by risk removed and by the disruption they bring, so admins accept the changes and they stick.
What you get
What lands on
your desk.
Each piece names the account, the path it takes to control, and the change that closes it.
The document
The privileged access report
Executive summary, privilege path graphs for your directories and cloud platforms, every finding with evidence, and a target model for how admin access should be granted and watched.
The working file
The privileged account register
Every privileged account, human or machine, with its rights, owner, last use, protection status and the recommended change. It doubles as your starting inventory for a PAM rollout.
The conversation
The admin team session
A working session with the people who hold the rights. We walk the paths to control, agree which standing access goes first, and plan around the workflows each change touches.
Client case studies
Real engagements.
Documented outcomes.
In their words
"ForgePath has become a trusted security partner for YHB. Their team understands how a CPA firm operates and has helped us build a security program that’s both practical and sustainable."
In their words
"ForgePath has become a trusted security partner for YHB. Beyond helping us comply with FTC Safeguards requirements, they provide the governance, oversight, and guidance we rely on to protect our firm and our clients’ data. Their team understands how a CPA firm operates and has helped us build a security program that’s both practical and sustainable."
Trusted by industry leaders.
Privilege questions
What admins
ask us.
Straight answers from the practitioners who do the work. If yours is not here, ask us directly.
No. A standard domain user can read most of what BloodHound needs from Active Directory, and read only roles cover the cloud platforms. Where a system needs more, we agree it in scoping and give it back at the end.
Not in this assessment. We map and verify the paths without exploiting them. If you want proof that a path works, an internal network penetration test can demonstrate it with a safe artifact.
Yes. We check what the tool covers against where privilege actually lives. Accounts outside the vault, shared credentials and vendor access often sit beyond it, and those gaps are what we find.
Only the people you name. The map is sensitive because it shows an attacker's shortest route, so we deliver it through a channel you choose and keep our copy only as long as you agree.
Ready?
Bring us
the problem.
One conversation with a senior practitioner who has carried this responsibility before. We will tell you what we would do, and whether it is us.








