---
sourceDocument: Australia Governance, Risk, and Compliance
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/de-DE/governance-risk-compliance

 Release :

    - australia

ft:locale :

    - de-DE

ft:publication_title :

    - Australia Governance, Risk, and Compliance

ft:clusterId :

    - grc

bundleId :

    - grc

workflow :

    - Technology


---

# DevOps Accelerator plugin

# DevOps Accelerator plugin {#ariaid-title1}

* Freigeben Version: Australia
* 
* Aktualisiert 12. März 2026
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 Minuten Lesedauer

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).  
Wichtig:  
GRC DevOps Accelerator is now deprecated and no longer supported or available for new activation. For details, see the [Deprecation process \[KB0867184\]](https://hi.service-now.com/kb_view.do?sysparm_article=KB0867184) article in the Now Support Knowledge Base.

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 {#devops-accelerator-pace-pc__section_ftw_2lh_g5b}

1. Hierarchy of PaCE-related plugins and CDM-related plugins.
2. DevOps Config Policy Content Pack provided by PaCE.
3. GRC plugins: GRC: Cybersecurity Controls Accelerator, GRC: Compliance UCF, and GRC: Continuous Authorization and Monitoring.

{#devops-accelerator-pace-pc__ol_xz3_hnh_g5b}  
Hinweis:  
GRC: DevOps Accelerator (com.sn_grc_devops) is dependent on DevOps Config Policy Content Pack and GRC: Policy and Compliance Management. However, if GRC: Cybersecurity Controls Accelerator (CIS), GRC: Unified Compliance Framework (UCF), and GRC: Continuous Authorization and Monitoring (CAM) plugins are not installed on the instance, then the staging data relevant to the control objectives from these plugins would not be available on installing GRC: DevOps Accelerator.  
GRC: DevOps Accelerator plugin maps the relationship between PaCE policies and control objectives.  
Hinweis:  
Not all GRC control objectives may have a relationship with every PaCE policy.

## Populating control objective and PaCE mapping data from the instances to staging
table {#devops-accelerator-pace-pc__section_apc_q23_g5b}

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.  
    Abbildung : 1. Control objective to item table

DevOps policy to control objective staging table
:   Abbildung : 2. DevOps accelerator staging table

    There is a staging table as a part of DevOps accelerator, which is DevOps policy to control
    objective staging \[sn_grc_devops_policy_control_objective_staging\] table. A user with
    Compliance admin role can view the table.

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 {#devops-accelerator-pace-pc__section_dmz_kdj_g5b}

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.