CyberArk implementation & integration
A PAM platform is judged on the day an auditor asks who used a domain admin account last Tuesday. We build CyberArk so that the answer takes seconds, not a week.
What we deploy
Every component of a self-hosted CyberArk platform, sized and hardened for the way your teams will actually use it.
- Digital Vault
- The encrypted core, also called EPV11EPV stands for Enterprise Password Vault, the historical name of the Digital Vault. Most CyberArk engineers still just say “the Vault”.. Primary and DR vaults, replication, backup and restore tested before go-live, hardened servers.
- PVWA
- The web portal for users and administrators: authentication methods, MFA, load balancing, and the permission model your auditors will read.
- CPM
- The password manager behind the scenes: platform policies, rotation and reconciliation, so that verification failures are rare and visible.
- PSM & PSMP
- Isolated, recorded sessions for RDP, SSH, databases and web consoles, with connection components tuned for each target.
- Credential Providers
- CP and CCP (formerly AIM), so that applications and scripts stop carrying passwords in their configuration files.
- HTML5 gateway & PTA
- Browser-based access without a local client, and threat analytics on privileged activity.
Integrations that make it usable
A vault nobody can log into is a very secure paperweight. Most of the effort in a successful deployment goes into the places where CyberArk meets the rest of your estate:
- Directory and identity: LDAP and Active Directory mapping, directory migrations, group-based access to safes.
- Strong authentication: PKI and smart cards, RADIUS or SAML MFA, including an RDP proxy with certificate authentication for administrators.
- Logs and evidence: syslog to your SIEM (ELK, Splunk, Sentinel, QRadar), so that every privileged session also leaves a trail outside the vault.
- Workflow: ticketing integration and dual control, so that access to the most sensitive accounts is requested, justified and approved.
- Targets: Windows and Unix servers, databases such as Oracle and SQL Server, network and security appliances (Fortinet, Juniper, Gigamon and others), cloud consoles.
How a deployment runs
- Discovery and designSafe model and naming, platform policies, rotation rules, break-glass procedures, sizing and architecture, written down before anything is installed.
- BuildHardened Vault and components, high availability and DR, monitoring. Built as code wherever your organisation allows it.
- Onboarding in wavesAccount discovery, onboarding by perimeter, and platform tuning until CPM verification is green and stays green.
- HandoverRunbooks, administrator training and operational indicators your team can follow without us.
A core platform for a few thousand accounts typically takes two to four months from design to the first onboarding wave. Onboarding then continues in waves, at the pace your teams can absorb.
Field notes
Telecom group
Group-wide point of contact for CyberArk: deployments of PSM, EPV, CPM, PVWA and Credential Providers, design and administration, security policies, and maintenance of an estate of more than 200,000 objects across 100,000 hosts. Integrations included drivers for Fortinet, Gigamon, Juniper and Oracle targets.
Corporate & investment bank
Deployment of the CyberArk suite (PSM, EPV, CPM, PVWA, Credential Providers), an RDP proxy with certificate authentication, a migration to a new LDAP directory and the move of syslog feeds to ELK.
Independent, by design
We are not a CyberArk or Palo Alto Networks reseller, and we carry no licence quota. That means we can tell you when a component isn't worth deploying yet, and we can work next to the partner who sold you the licences, or instead of them for the engineering.
Questions
Before you ask
How long does a CyberArk implementation take?
For a core self-hosted platform of a few thousand accounts, two to four months from design to the first onboarding wave is typical. Large estates are onboarded in waves over several quarters.
Self-hosted or Privilege Cloud?
Both. We deploy self-hosted Privileged Access Manager and Privilege Cloud, and we help you choose: the answer depends on your regulatory constraints, your operations team and your Idira roadmap more than on features.
Can you work with our existing integrator or reseller?
Yes. We often work alongside the partner that sold the licences, taking on the engineering-heavy parts: design, integrations, connectors and onboarding.
Do you deliver documentation?
Always: architecture and design decisions, runbooks, and a handover session for your team, in English or French.
● Next step
Tell us about your vaultVersion, size, deadline. We will tell you straight away whether we are the right people for it.