DOCSLIB.ORG

DB2 LUW Database Auditing

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
DB2 LUW Database Auditing Who's Knocking at Your Door? DB2 LUW Database Auditing Melanie Stopfer IBM Software Group Session Code: G15 10:30-11:30 AM May 18, 2012 | Platform: DB2 LUW Melanie Stopfer is a Consulting Learning Specialist and Developer for IBM Software Group. As a Certified DB2 9.7 Advanced Technical Expert and Certified Learning Facilitation Specialist, she has provided hands-on in-depth technical support to customers specializing in both data warehouse and transaction systems. She has worked with development labs and worldwide customers to provide DB2 solutions since 1988. She has received numerous awards for development and implementation of DB2 recovery, performance, administration and database upgrade and migration best practice solutions In 2009, Melanie was the first DB2 LUW speaker to be inducted into the IDUG Speaker Hall of Fame. She was named best overall speaker in 2012 and Top Ten Speaker at IDUG NA 2011, 2010, 2009, 2008, 2007,and IDUG EMEA 2011, 2010, 2009, 2008 and 2007. 1 Click to edit Master title style 2 Objectives • Describe the tasks for DB2 database auditing performed by the SYSADM user • List security administration tasks for DB2 databases that require the SECADM database authority in performing database level audits • Utilize the db2audit command in implement instance level auditing and to configure the audit data and archive locations • Create audit policies to enable collection of specific categories of audit data for a DB2 database • Assign audit policies to selected tables, users or database roles using the AUDIT statement • Understand auditing authority requirements Learn the configuration and management tasks required for implementation of DB2 instance or database level auditing. You will learn the specific tasks that need to be performed by a SYSADM (system administrator) or SECADM (security administrator) to setup and control auditing of DB2 environments, including use of the db2audit command. The creation of audit policies which can be assigned to specific tables, users or database roles to perform selective collection of audit records will be discussed. Objectives: •Describe tasks for DB2 database auditing performed by SYSADM user. •List security administration tasks for DB2 databases that require SECADM database authority in performing database level audits. •Utilize db2audit command to implement instance level auditing and configure audit data and archive locations. •Create audit policies to enable collection of specific categories of audit data for DB2 database. •Assign audit policies to selected tables, users or database roles using AUDIT statement. 2 DB2 Audit Facilities Prior to DB2 9.5 • Auditing facilities controlled by SYSADM user • Audit operates at the DB2 instance level • db2audit command used to manage audit processing – db2audit configure – To select audit options – db2audit describe – To display current audit status – db2audit start/stop – To control operations – db2audit extract – To extract audit records from the active audit log – db2audit prune – To remove audit records from the active audit log $HOME/sqllib/security db2audit.cfg db2audit.log audit.del checking.del objmaint.del secmaint.del sysadmin.del validate.del context.del 3 Prior to DB2 9.5, the facilities for auditing of DB2 databases were based on using the db2audit command, which required a user with SYSADM authority. The db2audit command operates at the instance level, so the types of audit data collected and the option to enable and disable auditing impacted all of the databases running under the same instance. •The audit configuration file and the audit log file were stored at a fixed location, the security subdirectory of the sqllib path for the instance. •The extract option of the db2audit command was used to extract audit records from the active audit log file for the instance. •The prune option of the db2audit command was used to remove older audit data from the active audit log file. 3 Standard DB2 Audit Data Categories • AUDIT – Generates records when audit settings are changed or when the audit log is accessed. • CHECKING – Generates records during authorization checking of attempts to access or manipulate DB2 database objects or functions. • OBJMAINT – Generates records when creating or dropping data objects. • SECMAINT – Generates records when granting or revoking: object or database privileges, or DBADM authority. Records are also generated when the database manager security configuration parameters SYSADM_GROUP, SYSCTRL_GROUP, or SYSMAINT_GROUP are modified. • SYSADMIN – Generates records when operations requiring SYSADM, SYSMAINT, or SYSCTRL authority are performed. • VALIDATE – Generates records when authenticating users or retrieving system security information. • CONTEXT – Generates supporting detailed records, like the SQL statement for dynamic SQL. 4 DB2 provides options to select the types of audit records that can be generated by a DB2 database. There are also options to choose whether an audit record should be generated by normal successful activity, like an authorized database connection request, compared to a failed request, like a connection that is rejected because the password is incorrect or expired. There are different categories of audit records that may be generated. The categories of events available for auditing are: •Audit (AUDIT). Generates records when audit settings are changed or when the audit log is accessed. •Authorization Checking (CHECKING). Generates records during authorization checking of attempts to access or manipulate DB2 database objects or functions. •Object Maintenance (OBJMAINT). Generates records when creating or dropping data objects. •Security Maintenance (SECMAINT). Generates records when granting or revoking: object or database privileges, or DBADM authority. Records are also generated when the database manager security configuration parameters SYSADM_GROUP, SYSCTRL_GROUP, or SYSMAINT_GROUP are modified. •System Administration (SYSADMIN). Generates records when operations requiring SYSADM, SYSMAINT, or SYSCTRL authority are performed. •User Validation (VALIDATE). Generates records when authenticating users or retrieving system security information. •Operation Context (CONTEXT). Generates records to show the operation context when a database operation is performed. This category allows for better interpretation of the audit log file. When used with the log's event correlation field, a group of events can be associated back to a single database operation. For example, a query statement for dynamic queries, a package identifier for static queries, or an indicator of the type of operation being performed, such as CONNECT, can provide needed context when analyzing audit results. The SQL or XQuery statement providing the operation context might be very long and is completely shown within the CONTEXT record. This can make the CONTEXT record very large. 4 Limitations for Audit Support Prior to DB2 9.5 • Lack of flexibility: – All databases in instance are controlled by a single audit configuration. – Audit log file resides in a fixed location. For DPF databases, this may be a NFS shared file system. – Can select type of audit data but no way to limit auditing to selected users or certain tables. – Dynamic SQL text only available using CONTEXT option which generates a large volume of data. • Performance impact: – Extracting audit data from the active audit log can impact database performance. – General performance issues when producing a large volume of audit data. 5 In order to address the major limitations of database auditing in previous DB2 releases, DB2 9.5 improved and extended the facilities for database auditing. For example prior to DB2 9.5: •The db2audit command set auditing option for the DB2 instance, so all of the databases in the instance are controlled by that single audit configuration. •The Audit log file resides in a fixed location. For DPF databases, this may be a NFS shared file system. •The configuration allowed the administrator to select categories of audit data but there was no method to limit auditing to selected users or certain tables •If the audit requirements included the SQL statement text, the generation of Dynamic SQL text required using the CONTEXT option which generates a large volume of data. •The EXTRACT option of the db2audit command retrieved data from the active audit file, which could impact database performance Beginning with DB2 9.5, the audit facilities were enhanced, including these options: •The location for the active audit log files can be configured. This makes it easier for DPF partitioned databases to specify a local disk on each database server to hold the audit data. •Auditing can be enabled and configured at the database or instance level. •The generation of audit records can be limited to activity for selected users or tables. 5 DB2 9.5 & 9.7 Database Audit Features – Part 1 • Two distinct and independent methods for auditing database activity: – Instance level audit: • db2audit command utilized to configure and manage instance level audit data collection Requires SYSADM authority – Database level audit: • Management requires SECADM authority for the DB2 database • SECADM creates audit policy objects in a database using CREATE AUDIT POLICY statements • SECADM uses the AUDIT statement to assign an audit policy to the database or to some specific type of activity, including a table, a defined database role or an individual user • DB2 provided Stored procedures may be used by SECADM user to archive database audit data and
Load more

Recommended publications
  • Integrigy Obtaining Value from Your Database Activity Monitoring Solution
    Obtaining Value from Your Database Activity Monitoring (DAM) Solution September 23, 2015 Mike Miller Stephen Kost Phil Reimann Chief Security Officer Chief Technology Officer Director of Business Development Integrigy Corporation Integrigy Corporation Integrigy Corporation Agenda How to Obtain Overview Value 1 2 3 4 DAMs & Q&A How They Work About Integrigy ERP Applications Databases Oracle E-Business Suite Oracle, SQL Server, MySQL Products Services Verify Security Assessments Validates Security Oracle EBS, Apex, OBIEE, Databases, Security AppSentry Sensitive Data, Penetration Testing ERP Application and Database Security Auditing Tool Ensure Compliance Compliance Assistance SOX, PCI, HIPAA Protects Oracle EBS AppDefend Build Enterprise Application Firewall Security Security Design Services for the Oracle E-Business Suite Auditing, Encryption, DMZ You Agenda How to Obtain Overview Value 1 2 3 4 DAMs & Q&A How They Work Security is a Process . Tools do not provide security, people do - Tools only enable and automate . Security is not provided by any one product, upgrade, or patch - Security provided by on-going lifecycle and configuration management . Database security is a process - Monitoring and auditing are only one of several components required to secure a database Database Security Program Components . An inventory of all databases and sensitive data locations Inventory . Methods and processes to maintain the inventories . A measureable database security standard and baseline Configuration . Periodic validation with compliance to the standard . Database access management policies, procedures, and tools Access . Database access profiling and monitoring . Database auditing requirements, processes, and definitions Auditing . Centralized auditing retention and reporting solution . Database real-time security monitoring and intrusion detection Monitoring . Database monitoring definition and tools .
    [Show full text]
  • Using IBM Infosphere Guardium for Monitoring and Auditing IBM DB2 for I Database Activity Ensure Compliance and Create a Tamper-Proof Audit Trail
    Using IBM InfoSphere Guardium for monitoring and auditing IBM DB2 for i database activity Ensure compliance and create a tamper-proof audit trail Kathryn Zeidenstein December 16, 2013 Mark J. Anderson (First published October 09, 2012) IBM® InfoSphere® Guardium® is an enterprise information audit and protection solution that helps enterprises to protect and audit information across a diverse set of relational and nonrelational data sources such as Oracle, Teradata, IMS, VSAM, Microsoft® SharePoint, and IBM Netezza®, and IBM DB2® for z/OS®, and DB2 for Linux, UNIX and Windows. With InfoSphere Guardium V9.0, DB2 for i can now be included as a data source, enabling you to monitor access through native interfaces and through SQL. This article provides a brief overview of the InfoSphere Guardium architecture, describes how to configure access (including best practices for performance), and describes how to access data activity reports. Overview InfoSphere Guardium is an enterprise information database audit and protection solution that helps enterprise protect and audit information across a diverse set of relational and nonrelational data sources such as Oracle, Teradata, IMS, VSAM, Microsoft SharePoint, IBM Netezza, and DB2 for z/OS and DB2 for Linux, UNIX and Windows. With InfoSphere Guardium V9.0, DB2 for i can now be included as a data source, enabling you to monitor accesses from native interfaces as well as through SQL. This article provides a brief overview of the InfoSphere Guardium architecture, describes how to configure access (including best practices for performance), and shows how to access data activity reports. A short introduction to InfoSphere Guardium The IBM InfoSphere Guardium solution evolved to address the particular needs of organizations that need to implement more automated and auditable data security practices.
    [Show full text]
  • Auditing Database Systems Through Forensic Analysis
    DePaul University Via Sapientiae College of Computing and Digital Media Dissertations College of Computing and Digital Media Summer 7-17-2020 Auditing database systems through forensic analysis James Wagner DePaul University, [email protected] Follow this and additional works at: https://via.library.depaul.edu/cdm_etd Part of the Computer and Systems Architecture Commons, and the Data Storage Systems Commons Recommended Citation Wagner, James, "Auditing database systems through forensic analysis" (2020). College of Computing and Digital Media Dissertations. 23. https://via.library.depaul.edu/cdm_etd/23 This Dissertation is brought to you for free and open access by the College of Computing and Digital Media at Via Sapientiae. It has been accepted for inclusion in College of Computing and Digital Media Dissertations by an authorized administrator of Via Sapientiae. For more information, please contact [email protected]. AUDITING DATABASE SYSTEMS THROUGH FORENSIC ANALYSIS BY JAMES WAGNER A DISSERTATION SUBMITTED TO THE SCHOOL OF COMPUTING, COLLEGE OF COMPUTING AND DIGITAL MEDIA OF DEPAUL UNIVERSITY IN PARTIAL FULFILLMENT OF THE REQUIREMENTS FOR THE DEGREE OF DOCTOR OF PHILOSOPHY DEPAUL UNIVERSITY CHICAGO, ILLINOIS 2020 DePaul University College of Computing and Digital Media Dissertation Verification This doctoral dissertation has been read and approved by the dissertation committee below according to the requirements of the Computer and Information Systems PhD program and DePaul University. Name: James Wagner Title of dissertation: AUDITING DATABASE SYSTEMS THROUGH FORENSIC ANALYSIS Date of Dissertation Defense: 07/17/2020 Alexander Rasin Dissertation Advisor* Boris Glavic st 1 Reader Tanu Malik 2nd Reader Jacob Furst 3rd Reader Karen Heart 4th Reader (if applicable) 5th Reader (if applicable) * A copy of this form has been signed, but may only be viewed after submission and approval of FERPA request letter.
    [Show full text]
  • Auditing the DBA in Oracle Applications: a Guide for Compliance and Audit Managers
    www.absolute-tech.com White Paper Auditing the DBA in Oracle Applications: A Guide for Compliance and Audit Managers By Cameron Larner Absolute Technologies, Inc. Copyright ©2014 by Cameron Larner Page 1 of 28 www.absolute-tech.com Table of Contents Introduction .......................................................................................................... 3 Intended Audience ................................................................................................ 3 Background ........................................................................................................... 3 Objectives ............................................................................................................. 3 DBA and Database Basics ...................................................................................... 4 DBA’s Primary Functions .................................................................................... 4 Database Objects............................................................................................... 4 Database Access ................................................................................................ 7 Database Operations ......................................................................................... 7 DBA Access to Oracle / E-Business Suite ........................................................... 8 Approaches to Auditing the DBA ......................................................................... 16 SQL Audit ........................................................................................................
    [Show full text]
  • Event Log Sql Schema
    Event Log Sql Schema Demythologized Dyson usually disforests some embranchment or exudes injudiciously. Diastyle Floyd gravitated hesitatingly, he dilutes his aerophones very discommodiously. Carson receipt plaguily? The schema changes to not tracked for all the batch of information we know how google cloud sql server express edition, log event sql schema changes from Triggering repairs at and time. Can by adding or schema acts as i did this lets us avoid using multi factor authentication, schemas in sub query, or numeric and discover all. Represents a schema in case, as a new schema by updating capture instance exec sys user as needed in different drive than others in object and log event sql schema changes event. SQL Server Audit Log Events after Translation by LOGbinder for SQL Server. The login i will be avoided unless absolutely necessary event log sql schema changes can configure log is not available disk crash, is not available inside ddl from? Supported pipeline types Data Collector The SQL Server CDC Client origin processes data in Microsoft SQL. There are ignored by your own advantages to. You enable allow throttling of business. Microsoft SQL Server is a relational database management system developed by Microsoft. Kafka connect service to make sure to record in a file, with additional documentation, availability in this category to execute all kinds of etl. One breach the assumptions that I would interest you to reconsider is telling you need want and have different tables for each event either or if over these event types are. The kettle table shows the schema for the event_data and event_data_historical database tables.
    [Show full text]
  • Mcafee Real-Time Database Monitoring, Auditing, and Intrusion
    White Paper McAfee Real-Time Database Monitoring, Auditing, and Intrusion Prevention Table of Contents Introduction 3 Existing Components of Database Security 3 Authentication and access control 3 Native database audit tools 4 The Network Approach to Database Activity Monitoring 4 The local access challenge 4 The encryption challenge 6 McAfee Database Activity Monitoring: Real-Time Database Monitoring 7 and Intrusion Prevention Unique advantages 11 2 McAfee Real-Time Database Monitoring, Auditing, and Intrusion Prevention Databases store an enterprise’s most valuable information assets, but in most organizations today, they are poorly protected. It’s good common sense to secure databases as well as or better than other systems in the enterprise. But it’s not that simple. In this white paper, we take a look at the shortcomings of the database security tools used by enterprises worldwide and the technology and approach required to provide real-time, comprehensive protection for all types of databases. Components of Database Security A wide array of technologies and tools are currently used to provide various aspects of database security. As with other areas of IT security, no single tool can provide an ironclad defense against all threats and abuses. It’s best to implement a combination of tools to achieve adequate security. The two main categories of tools in use across enterprises large and small are authentication/access “I hack, I ruin, I make piles of control and native database audit tools. money.” Authentication and access control —Andrew Auernheimer The ability to designate roles, logins, and passwords is the most basic and most widely used level of (Charged in US Federal Court with database security.
    [Show full text]
  • Database Auditing Essentials.Pdf
    Database Auditing Who did what to which data when and how? INTELLIGENCE. INNOVATION. INTEGRITY Authors This presentation was prepared by: Craig S. Mullins Corporate Technologist NEON Enterprise Software, Inc. 14100 Southwest Freeway Sugar Land, TX 77479 Tel: 888.338.6366 Fax: 281.207.4973 E-mail: [email protected] This document is protected under the copyright laws of the United States and other countries as an unpublished work. This document contains information that is proprietary and confidential to NEON Enterprise Software, which shall not be disclosed outside or duplicated, used, or disclosed in whole or in part for any purpose other than to evaluate NEON Enterprise Software products. Any use or disclosure in whole or in part of this information without the express written permission of NEON Enterprise Software is prohibited. © 2006 NEON Enterprise Software (Unpublished). All rights reserved. INTELLIGENCE. INNOVATION. INTEGRITY Agenda Emergence of Enterprise Data Protection Regulatory Compliance and Auditing Database Auditing Capabilities INTELLIGENCE. INNOVATION. INTEGRITY DBA versus Data Management Database Administration Data Management — Database Security — Data Protection — Backup/Recovery — Data Privacy Protection — Disaster Recovery — Data Quality Improvement — Reorganization — Data Quality Monitoring — Performance Monitoring — Application Call Level Tuning — Database Archiving — Data Structure Tuning — Data Extraction — Capacity Planning — Metadata Management Managing the database environment Managing the content
    [Show full text]
  • Agent Based System for Realtime Database Audit Monitoring
    UNIVERSITY OF NAIROBI SCHOOL OF COMPUTING AND INFORMATICS AGENT BASED SYSTEM FOR REALTIME DATABASE AUDIT MONITORING BY BONIFACE AKUKU P58/73079/2009 SUPERVISOR MR. CHRISTOPHER MOTURI August 2011 A research report submitted in partial fulfillment for the requirements of Master of Science in Computer Science University of NAIROBI Library 0439225 4 Table of Contents Table of Contents........................................................................................................................................ „... ii Abstract............................................................................................................................................................. iii Dedication......................................................................................................................................................... iv Acknowledgement..............................................................................................................................................v Declaration........................................................................................................................................................ vi Abbreviations...................................................................................................................................................vii List of Tables...................................................................................................................................................viii List of Figures...................................................................................................................................................ix
    [Show full text]
  • A Conceptual Framework of Information Security Database Audit and Assessment in University Based Organization
    A CONCEPTUAL FRAMEWORK OF INFORMATION SECURITY DATABASE AUDIT AND ASSESSMENT IN UNIVERSITY BASED ORGANIZATION MUNEEB UL HASAN A project report submitted in partial fulfillment of the requirements for the award of the degree of Master of Science (Information Security) Faculty of Computing Universiti Teknologi Malaysia MAY 2018 iii In the name of ALLAH, the Most Gracious and the Most Merciful To my beloved father and to my beloved mother may ALLAH bless them both who made me see further by standing on their shoulders, and to all my family and friends. Thank you. iv ACKNOWLEDGEMENT First and foremost, I would like to express heartfelt gratitude to my supervisor Dr. Siti Hajar Othman for his constant support during my study at UTM. She inspired me greatly to work in this project. Her willingness to motivate me contributed tremendously to our project. I have learned a lot from her and I am fortunate to have her as my mentor and supervisor Besides, I would like to thank the authority of Universiti Teknologi Malaysia (UTM) for providing me with a good environment and facilities such as Computer laboratory to complete this project with software which I need during process. Last but not the least, deepest gratitude goes to my beloved family members for their endless love, prayers and encouragement and to everyone who has been involved in this project even by coincidence. v ABSTRACT Today, databases are one of the most important things in the IT world and it is also becoming more popular and organizations globally are gradually moving their traditional IT setup to database model to gain the benefits of securing the data and in terms of providing easy access and elasticity of IT services.
    [Show full text]
  • Accelerate Your Database Activity Monitoring Readiness to Comply with Reserve Bank of India (RBI) Guidelines
    Accelerate your Database Activity Monitoring readiness to comply with Reserve Bank of India (RBI) Guidelines June 2020 | Version 20.01 Copyright © 2020, Oracle and/or its affiliates PURPOSE This technical white-paper provides an overview of Database Activity Monitoring requirements for compliance with the RBI Guidelines on Cyber Security. The white-paper is intended to help you accelerate your readiness to RBI compliance for Database Activity Monitoring requirements by leveraging Oracle Database’s native auditing feature, and Oracle Audit Vault and Database Firewall (AVDF) product. INTENDED AUDIENCE Intended audience would include key stakeholders like CIOs, CISOs, Executive Directors, business unit heads, heads of internal audit, operational risk, compliance and fraud management from all of the financial institutions regulated by RBI in Indian sub-continent. If you are responsible for designing, implementing, maintaining, or operating security controls for database systems, this paper is intended for you to help accelerate compliance with RBI guidelines on Database Activity Monitoring requirements. DISCLAIMER This document in any form, software or printed matter, contains proprietary information that is the exclusive property of Oracle. Your access to and use of this confidential material is subject to the terms and conditions of your Oracle software license and service agreement, which has been executed and with which you agree to comply. This document is not part of your license agreement nor can it be incorporated into any contractual agreement with Oracle or its subsidiaries or affiliates. This document is for informational purposes only and is intended solely to assist you in planning for the implementation and upgrade of the product features described.
    [Show full text]
  • Using Oracle Data Safe
    Oracle Cloud Using Oracle Data Safe E92975-42 June 2021 Oracle Cloud Using Oracle Data Safe, E92975-42 Copyright © 2019, 2021, Oracle and/or its affiliates. This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited. The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing. If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, then the following notice is applicable: U.S. GOVERNMENT END USERS: Oracle programs (including any operating system, integrated software, any programs embedded, installed or activated on delivered hardware, and modifications of such programs) and Oracle computer documentation or other Oracle data delivered to or accessed by U.S. Government end users are "commercial computer software" or "commercial computer software documentation" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, the use, reproduction, duplication, release, display, disclosure, modification, preparation of derivative works, and/or adaptation of i) Oracle programs (including any operating system, integrated software, any programs embedded, installed or activated on delivered hardware, and modifications of such programs), ii) Oracle computer documentation and/or iii) other Oracle data, is subject to the rights and limitations specified in the license contained in the applicable contract.
    [Show full text]
  • Database Activity Monitoring Is Evolving Into Database Audit and Protection
    14.01.13 Database Activity Monitoring Is Evolving Into Database Audit and Protection Database Activity Monitoring Is Evolving Into Database Audit and Protection 22 February 2012 ID:G00230083 Analyst(s): Jeffrey Wheatman VIEW SUMMARY Database security concerns, regulatory requirements and expanded vendor capabilities are driving the emergence of a class of technologies that Gartner now identifies as database audit and protection tools. Database activity monitoring tools are transforming into DAP suites. Overview EVIDENCE Database audit and protection (DAP) represents an important evolutionary advance from earlier More than 100 client inquiries have indicated a shifting database activity monitoring (DAM) tools. Security managers, database administrators (DBAs) and other set of requirements — moving from basic monitoring stakeholders who are concerned with protecting sensitive data in databases should evaluate these to more advanced needs such as discovery, prevention increasingly mature suites. and vulnerability management. Vendor briefings and other discussions with vendors have indicated aggressive road maps with expanded capabilities for Key Findings the short term, midterm and long term. Enterprises are increasingly concerned with database security as they grapple with repositories containing huge and growing amounts of regulated and otherwise sensitive or critical data. The DAP market continues to mature, with vendors expanding their offerings and targeting a broader range of use cases. However, it is not yet clear whether enterprises will be willing or able to adopt some of the more advanced functions of DAP. Many enterprises do not possess the necessary program maturity, resources and skills to implement some of the more sophisticated DAP features that are becoming available. Legal and regulatory compliance drivers are still the most prevalent drivers for DAP investments, and Gartner expects this to be the case through the midterm.
    [Show full text]