Getting started with Database Security

Moraph resells, implements and runs Imperva database activity monitoring for the databases that hold customer, account and transaction data. Imperva records the queries run against those databases, applies the policies you approve, and raises alerts on activity such as unusually large reads of sensitive tables. Moraph tunes the policies, triages the alerts with your security team, and produces the audit evidence your examiners and auditors ask for.

What it is for

Customer data sits in a handful of databases that many people and applications can reach: database administrators, developers with production access, reporting tools and service accounts. Native database logging is often turned off for performance or kept where the administrators who generate it can also change it. When a large extract happens, nobody may notice until the data appears somewhere it should not. Monitoring tools that are installed but not tuned produce so many alerts that the important ones are missed.

• No independent record of who read sensitive tables, or how much
• Database administrators control the same logs that would record their activity
• Bulk reads by service accounts and reporting tools are hard to tell apart from misuse
• Monitoring policies left at defaults produce alerts nobody has time to review

Who uses it

• CISOs and information security officers at banks, credit unions, broker-dealers and lenders
• Database and infrastructure teams who run the databases behind core banking and lending
• Security operations teams who investigate data access
• IT audit and compliance teams responsible for database access controls
• Institutions that own Imperva but need it tuned and operated

Before you start

• Your organization uses Database Security as a managed platform from Moraph, under an agreement that covers it.
• Licences for Imperva, 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 Database Security 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 Database Security
• Everyday tasks
• Connect your systems
• Security, data and compliance
• Troubleshooting and the support guide
• Product overview on moraph.com