InfoSphere Guardium data security and protection for MongoDB Part 2, Configuration and policies

Protect and secure a new generation of databases

From the developerWorks archives

Indrani Ghatare, Matt Kalan, Sundari Voruganti, and Kathryn Zeidenstein

Date archived: January 13, 2017 | Last updated: September 16, 2014|First published: June 13, 2013

This article series describes how to monitor and protect MongoDB data using IBM InfoSphere® Guardium®, including the configuration of the solution, sample monitoring use cases, and additional capabilities such as quick search of audit data and building a compliance workflow using an audit process. Part 2 describes how to configure InfoSphere Guardium to collect MongoDB traffic and describes how to create security policy rules for a variety of typical data protection use cases, such as alerting on excessive failed logins, monitoring privileged users, and alerting on unauthorized access to sensitive data. Many organizations are just getting started with MongoDB, and now is the time to build security into the environment to save time, prevent breaches, and avoid compliance violations.

This content is no longer being updated or maintained. The full article is provided "as is" in a PDF file. Given the rapid evolution of technology, some steps and illustrations may have changed.



static.content.url=http://www.ibm.com/developerworks/js/artrating/
SITE_ID=1
Zone=Information Management, Security
ArticleID=933621
ArticleTitle=InfoSphere Guardium data security and protection for MongoDB Part 2: Configuration and policies
publish-date=09162014