Getting started with Privileged Access Management

Moraph resells, implements and runs CyberArk to control the privileged accounts that administer your core banking platform, databases, servers and network. CyberArk vaults and rotates the credentials, brokers and records administrator sessions, and requires approval where your policy says so. Moraph onboards the accounts, keeps the configuration aligned to your policy, watches the platform and its alerts, and gives your security team and auditors the evidence they ask for.

What it is for

The accounts that can change core banking configuration, read customer databases or rebuild servers are often the least controlled. Passwords are shared among administrators, kept in spreadsheets or scripts, and rarely changed. Vendors and contractors connect with standing access. When an examiner or auditor asks who used a domain administrator account on a given night and what they did, the answer depends on whoever remembers. Buying a privileged access platform fixes little on its own if nobody has time to find the accounts, onboard them and keep the policy current.

• Shared administrator passwords that are rarely rotated and known to too many people
• Service and application accounts with credentials hard-coded in scripts and configuration files
• Vendor and contractor access that stays open after the work is done
• No reliable record of what was done during an administrator session

Who uses it

• CISOs and information security officers at banks, credit unions and other financial institutions
• Infrastructure and core banking administrators who use privileged accounts every day
• IT risk and compliance teams who answer access findings
• Internal audit and examiners reviewing privileged access controls
• Institutions that own a CyberArk licence but have not finished rolling it out

Before you start

• Your organization uses Privileged Access Management as a managed platform from Moraph, under an agreement that covers it.
• Licences for CyberArk, bought through Moraph or under your own agreement with the vendor.
• A Moraph account in your organization for each person who works with Moraph on the service.
• Named technical and security contacts, recorded in the Moraph Portal.

Steps to get started

1. Agree the scope of the managed service for Privileged Access Management with Moraph, including which environments and teams it covers.

2. Name your administrators, technical contact and security contact in the Moraph Portal under People and access.

3. Review the configuration baseline Moraph proposes for your regulations, and record any changes you need.

4. Confirm how users will sign in, through your identity provider where the platform supports it.

5. Agree the pilot group and the cut-over plan with your Moraph delivery lead.

Where to go next

• Onboard Privileged Access Management
• Everyday tasks
• Connect your systems
• Security, data and compliance
• Troubleshooting and the support guide
• Product overview on moraph.com