DevOps Accelerator plugin
Summarize
Summary of DevOps Accelerator plugin
The DevOps Accelerator plugin is an application designed to help customers evaluate compliance with DevOps policies and Governance, Risk, and Compliance (GRC) control objectives by integrating with the Policy as a Code Engine (PaCE). It maps control objectives from various regulations and standards such as CIS controls, NIST 800-53, ISO 27002, and PCI DSS to DevOps policies provided by the DevOps Config Policy Content Pack. This integration enables monitoring of compliance status, visualization of PaCE execution evidence, and management of exceptions.
Show less
Important: The DevOps Accelerator plugin is deprecated and no longer supported or available for new activations.
Key Features
- Maps control objectives from regulatory frameworks to DevOps policies.
- Enables evaluation and monitoring of DevOps policy compliance within GRC.
- Visualizes evidence of PaCE policy execution for audit and compliance purposes.
- Supports exception management for compliance deviations.
- Automates data synchronization between control objectives and PaCE policies via scheduled jobs.
Pre-requisites and Dependencies
- Requires the DevOps Config Policy Content Pack from PaCE.
- Depends on GRC plugins: Cybersecurity Controls Accelerator (CIS), Compliance Unified Compliance Framework (UCF), Continuous Authorization and Monitoring (CAM), and Policy and Compliance Management.
- If some GRC plugins are not installed, related staging data for their control objectives will be unavailable.
- Requires a hierarchy of PaCE-related and Common Data Model (CDM)-related plugins.
Data Management and Processing
The plugin ships mapping data between control objectives and PaCE policies, stored in the Control objective to items table. This table records relationships where control objectives link to specific PaCE policies. The data initially populates a staging table in a Pending status and is processed daily by a scheduled job that moves valid records to the main mapping table, changing their status to Processed.
Records remain pending if corresponding control objectives or PaCE policies are not present in the instance, ensuring only relevant mappings are active.
GRC: DevOps Accelerator is an application that enables your customers to evaluate the compliance for DevOps policies and GRC control objectives integrating with Policy as a Code Engine (PaCE).
GRC: DevOps Accelerator (com.sn_grc_devops) plugin maps the control objectives drawn from regulations, standards, and frameworks, such as CIS controls, NIST 800-53, ISO 27002, PCI DSS, and others with DevOps Policy as a Code Engine (PaCE). The DevOps policies are provided by the DevOps Config Policy Content Pack.
With this integration you can evaluate the compliance status. The integration also enables the DevOps managers to monitor control compliance, visualize evidence of PaCE execution, and manage exceptions.
Pre-requisites for DevOps Accelerator
- Hierarchy of PaCE-related plugins and CDM-related plugins.
- DevOps Config Policy Content Pack provided by PaCE.
- GRC plugins: GRC: Cybersecurity Controls Accelerator, GRC: Compliance UCF, and GRC: Continuous Authorization and Monitoring.
Populating control objective and PaCE mapping data from the instances to staging table
- Control objective to items mapping table
- As part of DevOps accelerator, the mapping relationships between control objectives and PaCE policies are shipped to the customers. The relationship is captured in Control objective to items [sn_compliance_control_objective_item] table, where the Control objective column and Item record column, which is the PaCE policy, list the data.
For CAM and CIS, the sys IDs of the control objectives map with the DevOps policy sys IDs. However, for UCF the source ID of the control objective imported from the Shared List is mapped with the DevOps policy sys ID.
The data in the DevOps policy to control objective staging [sn_grc_devops_policy_control_objective_staging] table is shipped in Pending status. The data is populated in the staging table based on the applications that are installed in the instance. The data is not processed if the control objective and the PaCE policy do not exist in the instance.
Scheduled job to move data from the staging to the main table
A daily job (Import DevOps policy to Control Objective mapping from staging) runs after the applications and the DevOps accelerator are installed to add the records to the Control objective to items (sn_compliance_control_objective_item) table. If the record is successfully added to the mapping table, then the status of the record in the staging table moves to Processed. If a control objective is not populated or present in the application, then the record is not processed but is in Pending status.