--- sourceDocument: Brazil Governance, Risk, and Compliance sourceDocumentLink: https://www.servicenow.com/docs/r/governance-risk-compliance Release : - brazil ft:locale : - en-US ft:publication_title : - Brazil Governance, Risk, and Compliance ft:clusterId : - grc bundleId : - grc workflow : - Technology --- # Privacy content accelerator # Privacy content accelerator {#ariaid-title1} Release version: Brazil Updated September 10, 2026 ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 5 minutes to read Summarize ![AI sparkle icon](https://servicenow.com/docs/portal-asset/ai-sparkle-icon) Summarized using AI This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete. ## Summary of Privacy Content Accelerator The Privacy Content Accelerator in ServiceNow provides prebuilt privacy content that can be activated directly from the Privacy Workspace. It includes authority documents, citations, control objectives, and risk statements aligned with major privacy regulations such as GDPR, CCPA, LGPD, NIST Privacy Framework, and others. This accelerator helps ServiceNow customers efficiently manage privacy compliance content but does not guarantee regulatory compliance; customers remain responsible for their adherence to applicable laws. Show full answer Show less Access to the Privacy Content Accelerator is restricted to users with privacy manager or privacy admin roles. ## Content Organization and Access The accelerator interface has two main tabs: * **Privacy Frameworks:** Lists available authority documents with counts of related citations and control objectives. * **Risk Statements:** Shows risk statement categories with version details and options to activate or update them. Each tab is divided into two sub-tabs based on content installation state: * **Inactive:** Content not yet installed, showing an Activate button. * **Active:** Content currently installed, showing the active version number and an Update button. ## Content Status and Installation Authority documents and risk statements have statuses indicating whether their versions are new (not installed) or active (installed). Activating or updating content launches an installation wizard displaying related citations, control objectives, and risk statements for review. All citations, control objectives, and risk statements are AI-generated and must be reviewed for accuracy and relevance before mapping to processing activities or assessments. ## Installation Details and Versioning During installation, records transition from a "Ready" state (not yet installed) to "Installed" (active in the library). When updating risk statements to a new version, previously installed statements appear as "Ready" again. Reinstalling them may overwrite specific fields. Installation behavior for records with matching names includes: * **Citations:** Overwrite existing records within the same authority document. * **Risk Statements:** Overwrite existing records sharing the same name and category (all privacy risk statements share one category). Fields overwritten in risk statements during update include Description, Expected ALE Level, Tolerance status, Active status, Leaf License, Order, and State. Other changes remain intact. ## Best Practices for Customers * Review AI-generated content carefully for accuracy and alignment with your internal taxonomy before applying it. * Prior to updating risk statements, check for any custom changes. To preserve modifications, rename records before update to prevent overwriting. * Use the installation wizard to manage activation and updates efficiently while maintaining content integrity. The privacy content accelerator provides prebuilt privacy content that you can activate directly from the Privacy Workspace. ## Disclaimer Important: The ServiceNow Risk products help customers address regulatory requirements under various jurisdictions. However, we do not guarantee compliance and customers are ultimately responsible for their own compliance with applicable regulations. ServiceNow aims to provide software updates for new or updated major regulations and requirements within twelve to eighteen months of the regulation's publication. For regulations for which ServiceNow provides a level of support in the base system, ServiceNow aims to provide software updates for minor regulatory changes within 12 months and for major regulatory changes within up to 18 months depending on scope and impact. We differentiate between typical regulatory content updates, which do not require software updates or enhancements, and regulatory updates, which do require software updates or enhancements. Content updates are generally delivered on a shorter cadence than if software update or enhancement is required for the regulatory update or change. ## Accessing the privacy content accelerator {#privacy-content-accelerator__id_ujh_3c1_43c} Privacy Management Content provides prebuilt authority documents, citations, control objectives, and risk statements. These are aligned with major privacy frameworks, such as GDPR, CCPA, LGPD, NIST Privacy Framework 1.0, Virginia Consumer Data Protection Act (CDPA), Colorado Privacy Act, and DPDPA. A dedicated icon in the Privacy Workspace provides navigation to the privacy content accelerator. Only users with the privacy manager or privacy admin roles can access this icon. ## Content tab {#privacy-content-accelerator__section_rwh_kc1_43c} The privacy content accelerator page contains two tabs: Privacy Frameworks : Displays the available authority documents. Each authority document card shows the count of related citations and control objectives. Risk Statements : Displays risk statement categories. Each category card shows the version and provides an option to activate or update the associated risk statements. Note: The cards also show the current status, and the version number when an active version exists. Both tabs organize content into two sub-tabs by installation state: Inactive : Lists the authority documents and risk statement versions that aren't installed in your library. Cards on this sub-tab show the Activate button. To install content from this sub-tab, see [Activate privacy content](https://www.servicenow.com/docs/tsnScWqfJPNBsdecfrp7~g "Activate an authority document or risk statement version to install the associated citations, control objectives, or risk statements into your privacy library."). Active : Lists the authority documents and risk statement versions currently installed in your library. Cards on this sub-tab show the active version number and the Update button. To update the activated content in your library, see [Update content in the privacy library](https://www.servicenow.com/docs/ZUM7OoIW~PCL2VKYtVfM6A "Update an installed authority document or risk statement version to add newer citations, control objectives, and risk statements to your privacy library."). ## Content status {#privacy-content-accelerator__section_fqs_pc1_43c} Each authority document and risk statement card shows one of the following statuses: New : The authority document or the risk statement version hasn't been installed. The card displays an Activate button. Active : The authority document or the risk statement version is installed. The card displays the active version number and an Update button. ## Installing content {#privacy-content-accelerator__installation-wizard} When you activate or update an authority document or a privacy risk statement version, the installation wizard opens. The wizard displays the list of citations and control objectives associated with the authority document, and risk statements available for the selected version. Note: Control objectives and risk statements are AI-generated. Although AI models are exposed to major privacy regulations, they aren't trained on the risk and compliance methodologies that your teams may use to derive a complete, consistent set of control objectives and risk statements from a regulation. Review each record for accuracy, scope, and fit with your internal taxonomy before you map it to processing activities or assessment questions. {#privacy-content-accelerator__table_rs_columns__entry__2} | Column name | Description | |-|-| | Name | Name of the citation, control objective, or risk statement. | | Description | Description of the citation, control objective, or risk statement. Note: All descriptions are AI-generated. Check AI-generated content for accuracy. | | Installation state | Current installation state of the record. After you activate or update privacy content, selected citations, control objectives, or risk statements transition from **Ready** to **Installed** . * Ready: Records that haven't yet been installed. * Installed: Records that are installed and active in your library. {#privacy-content-accelerator__ul_jvv_gw1_ljc} Important: When you update to a new version of privacy risk statements, previously installed risk statements also appear as Ready by default. While this doesn't mean that existing records are removed from the library, reinstalling them may overwrite certain fields. | | Parent | The parent record of the selected citations, control objectives, or risk statements. Note: If a parent citation has not been installed, the parent field on child citation records displays an empty value. The parent citation value is populated after the parent citation is installed. The same behavior applies to related control objectives. | | Supplemental guidance | Source regulatory text related to the citations. Note: Supplemental guidance is formatted using AI. Review all content for accuracy. If you don't see this column, add it using the Personalize fields option. | [Table 1. Privacy content installation wizard] {#privacy-content-accelerator__table_rs_columns} ## Content reference records {#privacy-content-accelerator__section_content_reference} When an authority document is activated, a content reference record is created in your library. This record stores the active version and links to all citations installed for that authority document. Each citation record, in turn, lists its associated control objectives. ## Risk statement versioning {#privacy-content-accelerator__section_edb_jwx_m3c} Privacy risk statements are shipped in versioned sets. Each new version includes the risk statements from the previous version and adds new ones. To activate a new version, see [Activate privacy content](https://www.servicenow.com/docs/tsnScWqfJPNBsdecfrp7~g "Activate an authority document or risk statement version to install the associated citations, control objectives, or risk statements into your privacy library."). When you activate a new risk statement version, all risk statements appear as Ready, even those installed in a previous version. Reinstalling existing records from a new version can overwrite certain fields if they share the same name. ## Overwrite behavior for existing records {#privacy-content-accelerator__section-override} Citations : If a citation with the same name already exists in the instance and it belongs to the same authority document, installing the content pack version overwrites the existing record. Risk statements : If a risk statement with the same name already exists in your instance, reinstalling it overwrites the existing record. : Figure 1. Risk statement overwrite behavior : When you select the risk statements to install, they are matched against the ones already in your library by their name and category. The category is the same for all privacy risk statements. Each privacy risk statement is therefore uniquely identified by its name. Unique records are installed as new. Matching records are overwritten.On each matched risk statement, all edits to the following fields are overwritten with values from the incoming record: * Description * Expected ALE * Level * Tolerance status * Active * Leaf * License * Order * State {#privacy-content-accelerator__ul_override_fields} All changes to the related lists and fields outside the ones listed above are preserved. : Before updating, review your library for risk statements changed since the last activation or update. If updating would overwrite a change you must retain, rename the record before updating. This creates a separate record of the reinstalled risk statement, preserving all changes in the old record.