[{"data":1,"prerenderedAt":819},["ShallowReactive",2],{"/en-us/blog/meet-regulatory-standards-with-gitlab":3,"navigation-en-us":43,"banner-en-us":453,"footer-en-us":463,"blog-post-authors-en-us-Abubakar Siddiq Ango":702,"blog-related-posts-en-us-meet-regulatory-standards-with-gitlab":716,"blog-promotions-en-us":757,"next-steps-en-us":809},{"id":4,"title":5,"authorSlugs":6,"authors":8,"body":10,"category":11,"categorySlug":11,"config":12,"content":16,"date":20,"description":17,"extension":26,"externalUrl":27,"featured":14,"heroImage":19,"isFeatured":14,"meta":28,"navigation":29,"path":30,"publishedDate":20,"rawbody":31,"seo":32,"slug":13,"stem":36,"tagSlugs":37,"tags":41,"template":15,"updatedDate":25,"__hash__":42},"blogPosts/en-us/blog/meet-regulatory-standards-with-gitlab.yml","Meet regulatory standards with GitLab security and compliance",[7],"abubakar-siddiq-ango",[9],"Abubakar Siddiq Ango","Guiding principles in the form of standards have consistently ensured the secure and reliable delivery of products and services to customers.\nThese standards, typically enforced by legally mandated organizations, regulate industries and prevent the spread of subpar products.\n\nIn the Information Technology (IT) sector, adhering to standards extends beyond the final product delivery; it encompasses the entire solution lifecycle. As every industry increasingly leverages various forms of technology to accelerate processes and boost efficiency, vast quantities of often sensitive data are generated, stored, and transmitted using IT tools and services. The improper handling of this data can cause severe consequences, potentially leading to financial losses in the [hundreds of millions of dollars](https://tech.co/news/data-breaches-updated-list).\n\nThis comprehensive guide explains global compliance standards and walks through how to meet regulatory standards with GitLab compliance and security policy management.\n\nArticle contents:\n\n- [Common IT compliance standards](#common-it-compliance-standards)\n- [Global and regional compliance standards](#global-and-regional-compliance-standards)\n    - [Country/regional regulations](#countryregional-regulations)\n    - [Industry-specific standards](#industry-specific-standards)\n- [Importance of continuous compliance](#importance-of-continuous-compliance)\n- [Regulatory compliance vs. self-imposed standards](#regulatory-compliance-vs.-self-imposed-standards)\n- [Compliance management](#compliance-management)\n- [Compliance management with GitLab](#compliance-management-with-gitlab)\n    - [Compliance frameworks and pipelines](#compliance-frameworks-and-pipelines)\n    - [Security policy management](#security-policy-management)\n        - [Scan execution policies](#scan-execution-policies)\n        - [Scan result policies](#scan-result-policies)\n        - [License approval policies](#license-approval-policies)\n    - [Audit management](#audit-management)\n        - [Preparing for audits](#preparing-for-audits)\n        - [Using GitLab audit logs effectively](#using-gitlab-audit-logs-effectively)\n        - [Audit events streaming](#audit-events-streaming)\n- [Best practices for compliance management](#best-practices-for-compliance-management)\n- [Learn more](#learn-more)\n\n## Common IT compliance standards\nRegulatory compliance standards take various forms and depend on the industry or region in which an organization operates. First, we will look at common compliance standards, followed by region and industry-specific standards.\n\n### HIPAA\n\nThe [Health Insurance Portability and Accountability Act (HIPAA)](https://www.hhs.gov/hipaa/index.html) is important legislation that has impacted the healthcare industry in the U.S. The main aim of HIPAA, passed in 1996, is to protect sensitive patient health information from being disclosed without the patient's consent or knowledge.\n\nIt is essential to safeguard patient privacy, ensure data security, and standardize electronic healthcare transactions. HIPAA has forced healthcare providers, insurers, and related entities to implement strict data protection measures, significantly reducing unauthorized access to medical records and enhancing patient trust.\n\n### GDPR\n\n[The General Data Protection Regulation (GDPR)](https://gdpr-info.eu/) is a significant European Union law that governs the protection of personal data. Implemented in 2018, GDPR establishes strict guidelines for organizations handling the personal information of EU residents. It grants individuals greater control over their data, including the right to access, rectify, and erase personal information held by companies. GDPR mandates that organizations obtain explicit consent before collecting or processing personal data and clearly explain the purpose of data collection. Non-compliance can result in substantial financial penalties.\n\nAlthough an EU regulation, GDPR has global implications, affecting any organization that processes EU residents' data. This legislation has prompted widespread changes in data handling practices and has heightened awareness of privacy issues worldwide.\n\n### NIST SSDF\n\nThe [NIST Secure Software Development Framework (SSDF)](https://csrc.nist.gov/Projects/ssdf) is a guide to help organizations make safer software. Created by the National Institute of Standards and Technology, it offers [basic practices for secure software development](https://about.gitlab.com/blog/comply-with-nist-secure-supply-chain-framework-with-gitlab/).\n\nThe SSDF focuses on four main areas: getting the organization ready, protecting the software, making well-secured software, and dealing with vulnerabilities. It helps companies think about security, including security protocols, during development and throughout the software supply chain.\n\nBy following these guidelines, organizations can create software with fewer weak points and handle problems more effectively. The SSDF is flexible and can work with different software development methods, making it useful for many organizations.\n\n### PCI DSS\n\nThe [Payment Card Industry Data Security Standard (PCI DSS)](https://www.pcisecuritystandards.org/) is a set of security rules for organizations that handle credit card information. Created by major credit card companies, it aims to protect cardholders' data and prevent fraud. PCI DSS requires businesses to build and maintain a secure network, protect cardholder data, use strong access control measures, regularly monitor and test networks, and maintain an information security policy. These rules apply to any company that accepts, processes, stores, or transmits credit card data.\n\nCompliance with PCI DSS is mandatory for these businesses, regardless of their size or transaction volume. By following these standards, companies can better safeguard sensitive financial information, reduce the risk of data breaches, and maintain customer trust. Regular audits ensure ongoing compliance with these important security measures.\n\n### ISO 27000\n\n[ISO/IEC 27000](https://www.iso.org/standard/iso-iec-27000-family) provides the foundational framework for the ISO/IEC 27000 family of standards, offering a comprehensive overview of information security management systems (ISMS). It establishes a standardized vocabulary by defining key terms and concepts, ensuring consistent understanding across organizations in the field of information security.\n\nThe standard outlines the core components and processes to establish and maintain an effective ISMS. This guidance enables organizations to systematically manage information security risks, protecting confidential data and intellectual property.\n\nAdherence to ISO/IEC 27000 allows organizations to build a robust ISMS, enhancing their resilience against cyber threats, safeguarding valuable information assets, and fostering stakeholder trust.\n\n> [Learn how GitLab can help you on your ISO 27001 compliance journey.](https://about.gitlab.com/blog/how-gitlab-can-support-your-iso-compliance-journey/)\n\n## Global and regional compliance standards\n\n### Country/regional regulations\n\nWhile compliance standards like HIPAA and GDPR are known globally, they are USA and EU standards respectively. They influence other regional standards around the globe but are only required for companies to adhere to where they handle data from, for example, the EU. Several countries have compliance standards that must be met if a company operates in such countries. Here are a few other country-specific standards:\n- [SOX](https://en.wikipedia.org/wiki/Sarbanes%E2%80%93Oxley_Act) (USA, Public companies): Sarbanes-Oxley Act. Mandates proper financial record-keeping and reporting for public companies.\n- [PIPEDA](https://www.priv.gc.ca/en/privacy-topics/privacy-laws-in-canada/the-personal-information-protection-and-electronic-documents-act-pipeda/) (Canada, Commercial businesses): Personal Information Protection and Electronic Documents Act. Governs how private sector organizations collect, use, and disclose personal information.\n- [PDPA](https://www.pdpc.gov.sg/overview-of-pdpa/the-legislation/personal-data-protection-act) (Singapore, All organizations): Personal Data Protection Act. Governs the collection, use, and disclosure of personal data by organizations.\n- [APPI](https://www.ppc.go.jp/files/pdf/Act_on_the_Protection_of_Personal_Information.pdf) (Japan, All industries): Act on the Protection of Personal Information. Regulates the use of personal information in Japan.\n- [LGPD](https://lgpd-brazil.info/) (Brazil, All industries): Lei Geral de Proteção de Dados. Brazil's data protection law is similar to GDPR.\n- [FISMA](https://www.cisa.gov/topics/cyber-threats-and-advisories/federal-information-security-modernization-act) (USA, Federal agencies): Federal Information Security Management Act. Defines a framework for managing information security for federal information systems.\n- [POPI Act](https://popia.co.za/) (South Africa, All sectors): The Protection of Personal Information Act promotes the protection of personal information processed by public and private bodies.\n- [PDPA](https://www.pwc.com/th/en/tax/personal-data-protection-act.html) (Thailand, All sectors): Personal Data Protection Act. Like GDPR, it regulates the collection, use, and disclosure of personal data in Thailand.\n- [PIPL](https://en.wikipedia.org/wiki/Personal_Information_Protection_Law_of_the_People%27s_Republic_of_China) (China, All sectors): Personal Information Protection Law. China's first comprehensive data protection law is similar to GDPR.\n- [NDPR](https://nitda.gov.ng/wp-content/uploads/2021/01/NDPR-Implementation-Framework.pdf) (Nigeria, All sectors): Nigeria Data Protection Regulation. Safeguards the rights of natural persons to data privacy.\n- [DIFC Data Protection Law](https://www.difc.ae/business/laws-and-regulations/legal-database/difc-laws/data-protection-law-difc-law-no-5-2020) (Dubai, Companies in Dubai International Financial Centre): Regulates the processing of personal data in the DIFC free zone.\n- [PDPA](https://www.pdp.gov.my/jpdpv2/laws-of-malaysia-pdpa/personal-data-protection-act-2010/?lang=en) (Malaysia, Commercial transactions): Personal Data Protection Act. Regulates the processing of personal data in commercial transactions.\n- [Privacy Act](https://www.ag.gov.au/rights-and-protections/privacy) (Australia, Government agencies, and some private sector organizations) regulates how personal information is handled by Australian government agencies and some private sector organizations.\n- [KVKK](https://www.kvkk.gov.tr/Icerik/6649/Personal-Data-Protection-Law) (Turkey, All sectors): Turkish Personal Data Protection Law. Regulates the processing of personal data and protects individual rights.\n\nThese standards reflect the growing global concern for data privacy and security. Many countries are developing their own frameworks inspired by established regulations like GDPR. Each standard is tailored to the specific legal, cultural, and economic context of its country.\n\n### Industry-specific standards\n\n- [PCI DSS](https://www.pcisecuritystandards.org/) (Financial Services): The Payment Card Industry Data Security Standard applies to all organizations that handle credit card information globally.\n- [ISO 27001](https://www.iso.org/standard/iso-iec-27000-family) (All industries) is an Information Security Management System standard that provides a framework for information security management practices.\n- [GAMP 5](https://qbdgroup.com/en/blog/gamp-categories/) (Pharmaceutical): Good Automated Manufacturing Practice. Guidelines for computerized systems in pharmaceutical manufacturing.\n- [ISO 13485](https://www.iso.org/standard/59752.html) (Medical Devices): Specifies requirements for a quality management system for medical device manufacturers.\n- [COBIT](https://www.isaca.org/resources/cobit) (IT Management): Control Objectives for Information and Related Technologies. Framework for IT management and IT governance.\n- [ITIL](https://en.wikipedia.org/wiki/ITIL) (IT Services) is an Information Technology Infrastructure Library, a set of detailed practices for IT service management.\n- [NIST CSF](https://www.nist.gov/cyberframework) (Cybersecurity): National Institute of Standards and Technology Cybersecurity Framework. Guidance on managing and reducing cybersecurity risk.\n- [WCAG](https://www.w3.org/WAI/standards-guidelines/wcag/) (Web Accessibility): The Web Content Accessibility Guidelines aim to make web content more accessible to people with disabilities.\n- [Basel III](https://www.bis.org/bcbs/basel3.htm) (Banking) is the international regulatory framework for banks, including IT risk management requirements.\n- [TISAX](https://portal.enx.com/en-US/TISAX/) (Automotive): Trusted Information Security Assessment Exchange. Information security assessment and exchange mechanism for the automotive industry. (Learn how [GitLab's TISAX certification](https://about.gitlab.com/blog/gitlab-drives-automotive-industry-information-security-with-tisax/) helps customers in the automotive industry.)\n\nThese standards apply across national boundaries to specific industries or aspects of IT, ensuring consistent practices and security measures globally within their respective domains.\n\n## Importance of continuous compliance\nOrganizations need to implement systems that ensure compliance with relevant regulatory requirements and can achieve this with continuous compliance. [Continuous software compliance](https://about.gitlab.com/solutions/compliance/) is essential to every industry, as it provides ongoing monitoring, assessment, and adjustment of an organization's systems, processes, and practices to ensure they consistently meet relevant standards and regulations.\n\nContinuous compliance is not just a regulatory checkbox but a strategic necessity for software development today. It empowers organizations to proactively navigate emerging threats, technological shifts, and regulatory changes while fostering stakeholder trust, operational efficiency, and competitive advantage in an increasingly complex business environment.\n\n## Regulatory compliance vs. self-imposed standards\n\nRegulatory compliance and self-imposed standards are two distinct approaches to organizational governance. Regulatory compliance involves adhering to mandatory laws and regulations set by external authorities, which have a broad scope and potential legal consequences for non-compliance. It focuses on meeting minimum legal requirements and is generally less flexible. Examples include GDPR, HIPAA, and SOX.\n\nIn contrast, self-imposed standards are voluntary guidelines adopted by organizations to improve quality, security, or performance. These can be tailored to specific needs, are highly adaptable, and typically aim to exceed minimum requirements. While failure to meet self-imposed standards may impact reputation, it usually doesn't have legal ramifications.\nThe key differences lie in their origin, motivation, adaptability, and scope. Many organizations implement both approaches to create a comprehensive quality, security, and performance management strategy.\n\n## Compliance management\n\nTo meet standards, organizations must evaluate the right [compliance metrics](https://advisory.kpmg.us/articles/2018/compliance-metrics.html) and integrate them into their standard operating procedures to provide insights that enable early detection and prevention of current and future compliance risks. Thus, there is a need for efficient [compliance management](https://about.gitlab.com/solutions/compliance/). Compliance management goes beyond checking off a checklist periodically; it's a comprehensive organization-wide continuous process.\n\n## Compliance management with GitLab\n\nGitLab provides features that allow organizations to create [compliance frameworks](https://docs.gitlab.com/user/group/compliance_frameworks/), [security policies](https://docs.gitlab.com/user/application_security/policies/), and [audit management](https://docs.gitlab.com/administration/audit_reports/). GitLab also enables compliance or leadership teams to monitor compliance metrics with [compliance reports](https://docs.gitlab.com/user/compliance/compliance_report/). Let's take a look at some of these features.\n\n### Compliance frameworks and pipelines\n\nOrganizations can create a [compliance framework](https://docs.gitlab.com/user/group/compliance_frameworks/) that identifies projects in GitLab that must meet defined compliance requirements, which can be enforced with [compliance pipelines](https://docs.gitlab.com/user/group/compliance_pipelines/). For example, a FinTech company can create a [default compliance framework](https://docs.gitlab.com/user/group/compliance_frameworks/#default-compliance-frameworks) for all projects, ensuring every stage of their software development lifecycle meets the PCI DSS requirements for handling cardholder data.\n\nThese requirements are then enforced by ensuring every change introduced to the codebase is sufficiently tested automatically with GitLab's [application security features](https://docs.gitlab.com/user/application_security/), which cover source code, dependencies, licenses, vulnerabilities in running application and infrastructure configurations. You can learn more about how GitLab helps you achieve PCI compliance and other [regulatory compliance](https://about.gitlab.com/solutions/software-compliance/) with compliance frameworks.\n\nThe following videos demonstrate setting up and using compliance frameworks and pipelines.\n\n**Video tutorial: Create compliance frameworks**\n\n\u003C!-- blank line -->\n\u003Cfigure class=\"video_container\">\n  \u003Ciframe src=\"https://www.youtube.com/embed/IDswzRI-8VQ\" title=\"How to setup Compliance Frameworks & Pipelines in GitLab\" frameborder=\"0\" allowfullscreen=\"true\"> \u003C/iframe>\n\u003C/figure>\n\u003C!-- blank line -->\n\n**Video tutorial: Enforce compliance pipelines**\n\n\u003C!-- blank line -->\n\u003Cfigure class=\"video_container\">\n  \u003Ciframe src=\"https://www.youtube.com/embed/jKA_e_jimoI\" title=\"GitLab Compliance Pipelines & Overriding Settings\" frameborder=\"0\" allowfullscreen=\"true\"> \u003C/iframe>\n\u003C/figure>\n\u003C!-- blank line -->\n\n### Security policy management\n\nSecurity and compliance teams can use GitLab to enforce compliance requirements by ensuring security scanners run in certain pipelines or require approval on merge requests when [security policies](https://docs.gitlab.com/user/application_security/policies/) are violated. GitLab supports [scan execution](https://docs.gitlab.com/user/application_security/policies/scan-execution-policies/) and [scan result](https://docs.gitlab.com/user/application_security/policies/scan-result-policies/) policies. These policies are defined in a dedicated [security policy project](https://docs.gitlab.com/user/application_security/policies/#security-policy-project) that separates duties between security and development teams. Security policies can be applied granularly at the group, sub-group, and project levels. The policies can be edited in rule mode, which uses the [policy editor](https://docs.gitlab.com/user/application_security/policies/#policy-editor), or by yaml mode.\n\n#### Scan execution policies\nScan execution policies can be configured to run on a specified [GitLab Runner](https://docs.gitlab.com/runner/), including the following:\n-  [Static Application Security Testing](https://docs.gitlab.com/user/application_security/sast/)\n- [Infrastructure as\nCode](https://docs.gitlab.com/user/application_security/iac_scanning/)\n- [Dynamic Application Security Testing](https://docs.gitlab.com/user/application_security/dast/)\n- [Secret Detection](https://docs.gitlab.com/user/application_security/secret_detection/)\n- [Container Scanning](https://docs.gitlab.com/user/application_security/container_scanning/)\n- [Dependency Scanning](https://docs.gitlab.com/user/application_security/dependency_scanning/)\n\nThe scan jobs can be run on schedule or anytime a pipeline runs. Compliance and security teams can use scan execution policies to periodically check on and proactively prevent vulnerability escalation as part of a vulnerability management strategy. They can also reinforce controls when new trends are observed from scan results.\n\n**Video tutorial: Set up security scan policies in GitLab**\n\n\u003C!-- blank line -->\n\u003Cfigure class=\"video_container\">\n  \u003Ciframe src=\"https://www.youtube.com/embed/ZBcqGmEwORA\" title=\"How to set up security scan policies in GitLab\" frameborder=\"0\" allowfullscreen=\"true\"> \u003C/iframe>\n\u003C/figure>\n\u003C!-- blank line -->\n\n#### Scan result policies\n\nScan result policies add required review and approval for merge requests when the results of specified security scans violate the policies' rules. For example, a policy can require a security team member to take action when a newly identified critical SAST vulnerability is detected. This way, security and compliance team members can support developers while ensuring the changes introduced to the codebase are secure and meet compliance requirements.\n\n**Video tutorial: Overview of GitLab Scan Result Policies**\n\n\u003C!-- blank line -->\n\u003Cfigure class=\"video_container\">\n  \u003Ciframe src=\"https://www.youtube.com/embed/w5I9gcUgr9U\" title=\"Overview of GitLab Scan Result Policies\" frameborder=\"0\" allowfullscreen=\"true\"> \u003C/iframe>\n\u003C/figure>\n\u003C!-- blank line -->\n\n#### License approval policies\nWhen selecting scan types for scan result policy rules, you can choose between security scan, the default behavior for scan result policies, and license scan, which helps ensure license compliance. License scanning depends on the output of the [dependency scanning](https://docs.gitlab.com/user/application_security/dependency_scanning/) [CI/CD](https://about.gitlab.com/topics/ci-cd/) job to check if identified licenses match specified criteria, then adds approval requirements before an open merge request can be merged. This is crucial to ensure that only dependencies with approved licenses are used in your organization.\n\n**Video demo: License approval policies**\n\n\u003C!-- blank line -->\n\u003Cfigure class=\"video_container\">\n  \u003Ciframe src=\"https://www.youtube.com/embed/34qBQ9t8qO8\" title=\"License Approval Policies Demo\" frameborder=\"0\" allowfullscreen=\"true\"> \u003C/iframe>\n\u003C/figure>\n\u003C!-- blank line -->\n\n### Audit management\n#### Preparing for audits\nAudits are essential for compliance management because they allow you to understand your organization's security and compliance posture. External audits required by regulators are often detailed and exhaustive. To prepare for them, organizations need to:\n- Determine which regulations or standards will be assessed and what areas of the organization will be examined.\n- Analyze past audit results and ensure any previously identified issues have been addressed.\n- Collect all relevant policies, procedures, and records that demonstrate compliance.\n- Before the official audit, an internal audit must be performed to identify and address any potential compliance gaps.\n- Brief employees on the audit process and their roles. Conduct training if necessary.\n- Ensure all required documentation is easily accessible and well-organized.\n- Ensure all compliance-related policies and procedures are up-to-date and aligned with current regulations.\n- Verify that all technical safeguards and controls are in place and functioning correctly.\n- Identify key personnel who may be interviewed and brief them on potential questions.\n- Address known issues: If any known compliance issues exist, develop and document plans to address them.\n\nTo enable your preparedness, GitLab features: [Audit Events](https://docs.gitlab.com/administration/audit_events/) and [Compliance Center](https://docs.gitlab.com/user/compliance/compliance_center/) give a detailed view of an organization's compliance.\n\n#### Using GitLab audit logs effectively\n\nYou want to know every action taken on the GitLab instance with [audit events](https://docs.gitlab.com/administration/audit_events/). Audit reports allow you to track every significant event, who performed it, and when. You can also generate detailed reports from audit events using [audit reports](https://docs.gitlab.com/administration/audit_reports/), allowing you to prove your compliance to auditors or regulators.\n\n![Audit events](https://res.cloudinary.com/about-gitlab-com/image/upload/v1750098755/Blog/Content%20Images/Blog/Content%20Images/image1_aHR0cHM6_1750098755493.png)\n\n[The compliance center](https://docs.gitlab.com/user/compliance/compliance_report/#compliance-violations-report) is a significant component of audit management in GitLab, giving visibility to your organization's compliance posture. Compliance reports detail every violation discovered with the [compliance violations report](https://docs.gitlab.com/user/compliance/compliance_center/compliance_violations_report/) and the frameworks used by projects within your organization with the compliance [frameworks report](https://docs.gitlab.com/user/compliance/compliance_center/compliance_frameworks_report/).\n\n![Meet regulatory requirements - image 2](https://res.cloudinary.com/about-gitlab-com/image/upload/v1750098756/Blog/Content%20Images/Blog/Content%20Images/image2_aHR0cHM6_1750098755493.png)\n\n\u003Ccenter>\u003Cem>Example of a compliance violations report from a parent GitLab group.\u003C/em>\u003C/center>\n\n![Meet regulatory requirements - image 3](https://res.cloudinary.com/about-gitlab-com/image/upload/v1750098755/Blog/Content%20Images/Blog/Content%20Images/image3_aHR0cHM6_1750098755495.png)\n\n\u003Ccenter>\u003Cem>Example of a compliance framework report for all projects in a group\u003C/em>\u003C/center>\n\n#### Audit events streaming\nMost organizations have existing systems to monitor activities in their systems in real-time. With [audit events streaming](https://docs.gitlab.com/administration/audit_event_streaming/) on GitLab, you can integrate third-party solutions like Splunk infrastructure monitoring or DataDog streams monitoring service for real-time audit events analytics. All audit events data are sent to the streaming destination (it's essential to stream to a trusted service). Audit events streaming can be [configured at top-level groups](https://docs.gitlab.com/administration/audit_event_streaming/#top-level-group-streaming-destinations) and at the [instance level](https://docs.gitlab.com/administration/audit_event_streaming/#instance-streaming-destinations) for self-managed GitLab instances.\n\n## Best practices for compliance management\n\nHere are some best practices for effective compliance management:\n- Establish a strong compliance culture that promotes organizational compliance awareness and ensures leadership commitment and support.\n- Develop a comprehensive compliance program with clear policies and procedures and regularly review the program to reflect regulation changes.\n- Implement risk assessment and management to regularly identify and assess compliance risks, prioritizing risks based on potential impact and likelihood.\n- Conduct regular compliance training tailored to specific roles and responsibilities for all employees.\n- Implement compliance management to automate compliance monitoring and compliance reporting where possible.\n- Perform internal audits to identify gaps and areas for improvement. It is also essential to consider external audits unbiasedly and use audit results to refine and improve compliance processes.\n- Stay informed about regulatory changes by assigning responsibility for monitoring regulatory updates and participating in industry associations and forums.\n- Integrate compliance into business processes, embed compliance checks into operational workflows, and consider compliance implications in strategic decision-making. Align compliance goals with business objectives\n- Develop response plans for potential compliance breaches and conduct mock scenarios to test readiness for incidents and violations.\n\n## Learn more\nCompliance is a continuous process of efficiently managing risk by implementing guardrails and monitoring compliance metrics. GitLab empowers organizations to fulfill regulatory standards with our [compliance management](https://about.gitlab.com/solutions/compliance/) features. With GitLab, you can improve the software supply chain experience, build more secure software faster, and maintain the trust of your users, clients, and community.\n\n> Learn more about compliance and security policy management with the [GitLab DevSecOps tutorial](https://gitlab-da.gitlab.io/tutorials/security-and-governance/devsecops/simply-vulnerable-notes/), which contains lessons covering the complete application security lifecycle in GitLab.\n\n## Read more\n- [Introducing GitLab Dedicated for Government](https://about.gitlab.com/blog/introducing-gitlab-dedicated-for-government/)\n- [How to ensure separation of duties and enforce compliance with GitLab](https://about.gitlab.com/blog/ensuring-compliance/)\n- [The ultimate guide to least privilege access with GitLab](https://about.gitlab.com/blog/the-ultimate-guide-to-least-privilege-access-with-gitlab/)","security",{"slug":13,"featured":14,"template":15},"meet-regulatory-standards-with-gitlab",false,"BlogPost",{"title":5,"description":17,"authors":18,"heroImage":19,"date":20,"body":10,"category":11,"tags":21,"updatedDate":25},"Compliance is more than one-off audits; it's a continuous process of managing risk by implementing guardrails and monitoring specific metrics. Learn how with this comprehensive guide.",[9],"https://res.cloudinary.com/about-gitlab-com/image/upload/v1750098739/Blog/Hero%20Images/Blog/Hero%20Images/AdobeStock_282096522_securitycompliance.jpeg_1750098739024.jpg","2023-08-17",[22,23,11,24],"DevSecOps","DevSecOps platform","public sector","2024-08-22","yml",null,{},true,"/en-us/blog/meet-regulatory-standards-with-gitlab","seo:\n  title: Meet regulatory standards with GitLab security and compliance\n  description: >-\n    Compliance is more than one-off audits; it's a continuous process of\n    managing risk by implementing guardrails and monitoring specific metrics.\n    Learn how with this comprehensive guide.\n  ogTitle: Meet regulatory standards with GitLab security and compliance\n  ogDescription: >-\n    Compliance is more than one-off audits; it's a continuous process of\n    managing risk by implementing guardrails and monitoring specific metrics.\n    Learn how with this comprehensive guide.\n  noIndex: false\n  ogImage: >-\n    https://res.cloudinary.com/about-gitlab-com/image/upload/v1750098739/Blog/Hero%20Images/Blog/Hero%20Images/AdobeStock_282096522_securitycompliance.jpeg_1750098739024.jpg\n  ogUrl: https://about.gitlab.com/blog/meet-regulatory-standards-with-gitlab\n  ogSiteName: https://about.gitlab.com\n  ogType: article\n  canonicalUrls: https://about.gitlab.com/blog/meet-regulatory-standards-with-gitlab\ncontent:\n  title: Meet regulatory standards with GitLab security and compliance\n  description: >-\n    Compliance is more than one-off audits; it's a continuous process of\n    managing risk by implementing guardrails and monitoring specific metrics.\n    Learn how with this comprehensive guide.\n  authors:\n    - Abubakar Siddiq Ango\n  heroImage: >-\n    https://res.cloudinary.com/about-gitlab-com/image/upload/v1750098739/Blog/Hero%20Images/Blog/Hero%20Images/AdobeStock_282096522_securitycompliance.jpeg_1750098739024.jpg\n  date: '2023-08-17'\n  body: >-\n    Guiding principles in the form of standards have consistently ensured the\n    secure and reliable delivery of products and services to customers.\n\n    These standards, typically enforced by legally mandated organizations,\n    regulate industries and prevent the spread of subpar products.\n\n\n    In the Information Technology (IT) sector, adhering to standards extends\n    beyond the final product delivery; it encompasses the entire solution\n    lifecycle. As every industry increasingly leverages various forms of\n    technology to accelerate processes and boost efficiency, vast quantities of\n    often sensitive data are generated, stored, and transmitted using IT tools\n    and services. The improper handling of this data can cause severe\n    consequences, potentially leading to financial losses in the [hundreds of\n    millions of dollars](https://tech.co/news/data-breaches-updated-list).\n\n\n    This comprehensive guide explains global compliance standards and walks\n    through how to meet regulatory standards with GitLab compliance and security\n    policy management.\n\n\n    Article contents:\n\n\n    - [Common IT compliance standards](#common-it-compliance-standards)\n\n    - [Global and regional compliance\n    standards](#global-and-regional-compliance-standards)\n        - [Country/regional regulations](#countryregional-regulations)\n        - [Industry-specific standards](#industry-specific-standards)\n    - [Importance of continuous\n    compliance](#importance-of-continuous-compliance)\n\n    - [Regulatory compliance vs. self-imposed\n    standards](#regulatory-compliance-vs.-self-imposed-standards)\n\n    - [Compliance management](#compliance-management)\n\n    - [Compliance management with GitLab](#compliance-management-with-gitlab)\n        - [Compliance frameworks and pipelines](#compliance-frameworks-and-pipelines)\n        - [Security policy management](#security-policy-management)\n            - [Scan execution policies](#scan-execution-policies)\n            - [Scan result policies](#scan-result-policies)\n            - [License approval policies](#license-approval-policies)\n        - [Audit management](#audit-management)\n            - [Preparing for audits](#preparing-for-audits)\n            - [Using GitLab audit logs effectively](#using-gitlab-audit-logs-effectively)\n            - [Audit events streaming](#audit-events-streaming)\n    - [Best practices for compliance\n    management](#best-practices-for-compliance-management)\n\n    - [Learn more](#learn-more)\n\n\n    ## Common IT compliance standards\n\n    Regulatory compliance standards take various forms and depend on the\n    industry or region in which an organization operates. First, we will look at\n    common compliance standards, followed by region and industry-specific\n    standards.\n\n\n    ### HIPAA\n\n\n    The [Health Insurance Portability and Accountability Act\n    (HIPAA)](https://www.hhs.gov/hipaa/index.html) is important legislation that\n    has impacted the healthcare industry in the U.S. The main aim of HIPAA,\n    passed in 1996, is to protect sensitive patient health information from\n    being disclosed without the patient's consent or knowledge.\n\n\n    It is essential to safeguard patient privacy, ensure data security, and\n    standardize electronic healthcare transactions. HIPAA has forced healthcare\n    providers, insurers, and related entities to implement strict data\n    protection measures, significantly reducing unauthorized access to medical\n    records and enhancing patient trust.\n\n\n    ### GDPR\n\n\n    [The General Data Protection Regulation (GDPR)](https://gdpr-info.eu/) is a\n    significant European Union law that governs the protection of personal data.\n    Implemented in 2018, GDPR establishes strict guidelines for organizations\n    handling the personal information of EU residents. It grants individuals\n    greater control over their data, including the right to access, rectify, and\n    erase personal information held by companies. GDPR mandates that\n    organizations obtain explicit consent before collecting or processing\n    personal data and clearly explain the purpose of data collection.\n    Non-compliance can result in substantial financial penalties.\n\n\n    Although an EU regulation, GDPR has global implications, affecting any\n    organization that processes EU residents' data. This legislation has\n    prompted widespread changes in data handling practices and has heightened\n    awareness of privacy issues worldwide.\n\n\n    ### NIST SSDF\n\n\n    The [NIST Secure Software Development Framework\n    (SSDF)](https://csrc.nist.gov/Projects/ssdf) is a guide to help\n    organizations make safer software. Created by the National Institute of\n    Standards and Technology, it offers [basic practices for secure software\n    development](https://about.gitlab.com/blog/comply-with-nist-secure-supply-chain-framework-with-gitlab/).\n\n\n    The SSDF focuses on four main areas: getting the organization ready,\n    protecting the software, making well-secured software, and dealing with\n    vulnerabilities. It helps companies think about security, including security\n    protocols, during development and throughout the software supply chain.\n\n\n    By following these guidelines, organizations can create software with fewer\n    weak points and handle problems more effectively. The SSDF is flexible and\n    can work with different software development methods, making it useful for\n    many organizations.\n\n\n    ### PCI DSS\n\n\n    The [Payment Card Industry Data Security Standard (PCI\n    DSS)](https://www.pcisecuritystandards.org/) is a set of security rules for\n    organizations that handle credit card information. Created by major credit\n    card companies, it aims to protect cardholders' data and prevent fraud. PCI\n    DSS requires businesses to build and maintain a secure network, protect\n    cardholder data, use strong access control measures, regularly monitor and\n    test networks, and maintain an information security policy. These rules\n    apply to any company that accepts, processes, stores, or transmits credit\n    card data.\n\n\n    Compliance with PCI DSS is mandatory for these businesses, regardless of\n    their size or transaction volume. By following these standards, companies\n    can better safeguard sensitive financial information, reduce the risk of\n    data breaches, and maintain customer trust. Regular audits ensure ongoing\n    compliance with these important security measures.\n\n\n    ### ISO 27000\n\n\n    [ISO/IEC 27000](https://www.iso.org/standard/iso-iec-27000-family) provides\n    the foundational framework for the ISO/IEC 27000 family of standards,\n    offering a comprehensive overview of information security management systems\n    (ISMS). It establishes a standardized vocabulary by defining key terms and\n    concepts, ensuring consistent understanding across organizations in the\n    field of information security.\n\n\n    The standard outlines the core components and processes to establish and\n    maintain an effective ISMS. This guidance enables organizations to\n    systematically manage information security risks, protecting confidential\n    data and intellectual property.\n\n\n    Adherence to ISO/IEC 27000 allows organizations to build a robust ISMS,\n    enhancing their resilience against cyber threats, safeguarding valuable\n    information assets, and fostering stakeholder trust.\n\n\n    > [Learn how GitLab can help you on your ISO 27001 compliance\n    journey.](https://about.gitlab.com/blog/how-gitlab-can-support-your-iso-compliance-journey/)\n\n\n    ## Global and regional compliance standards\n\n\n    ### Country/regional regulations\n\n\n    While compliance standards like HIPAA and GDPR are known globally, they are\n    USA and EU standards respectively. They influence other regional standards\n    around the globe but are only required for companies to adhere to where they\n    handle data from, for example, the EU. Several countries have compliance\n    standards that must be met if a company operates in such countries. Here are\n    a few other country-specific standards:\n\n    - [SOX](https://en.wikipedia.org/wiki/Sarbanes%E2%80%93Oxley_Act) (USA,\n    Public companies): Sarbanes-Oxley Act. Mandates proper financial\n    record-keeping and reporting for public companies.\n\n    -\n    [PIPEDA](https://www.priv.gc.ca/en/privacy-topics/privacy-laws-in-canada/the-personal-information-protection-and-electronic-documents-act-pipeda/)\n    (Canada, Commercial businesses): Personal Information Protection and\n    Electronic Documents Act. Governs how private sector organizations collect,\n    use, and disclose personal information.\n\n    -\n    [PDPA](https://www.pdpc.gov.sg/overview-of-pdpa/the-legislation/personal-data-protection-act)\n    (Singapore, All organizations): Personal Data Protection Act. Governs the\n    collection, use, and disclosure of personal data by organizations.\n\n    -\n    [APPI](https://www.ppc.go.jp/files/pdf/Act_on_the_Protection_of_Personal_Information.pdf)\n    (Japan, All industries): Act on the Protection of Personal Information.\n    Regulates the use of personal information in Japan.\n\n    - [LGPD](https://lgpd-brazil.info/) (Brazil, All industries): Lei Geral de\n    Proteção de Dados. Brazil's data protection law is similar to GDPR.\n\n    -\n    [FISMA](https://www.cisa.gov/topics/cyber-threats-and-advisories/federal-information-security-modernization-act)\n    (USA, Federal agencies): Federal Information Security Management Act.\n    Defines a framework for managing information security for federal\n    information systems.\n\n    - [POPI Act](https://popia.co.za/) (South Africa, All sectors): The\n    Protection of Personal Information Act promotes the protection of personal\n    information processed by public and private bodies.\n\n    - [PDPA](https://www.pwc.com/th/en/tax/personal-data-protection-act.html)\n    (Thailand, All sectors): Personal Data Protection Act. Like GDPR, it\n    regulates the collection, use, and disclosure of personal data in Thailand.\n\n    -\n    [PIPL](https://en.wikipedia.org/wiki/Personal_Information_Protection_Law_of_the_People%27s_Republic_of_China)\n    (China, All sectors): Personal Information Protection Law. China's first\n    comprehensive data protection law is similar to GDPR.\n\n    -\n    [NDPR](https://nitda.gov.ng/wp-content/uploads/2021/01/NDPR-Implementation-Framework.pdf)\n    (Nigeria, All sectors): Nigeria Data Protection Regulation. Safeguards the\n    rights of natural persons to data privacy.\n\n    - [DIFC Data Protection\n    Law](https://www.difc.ae/business/laws-and-regulations/legal-database/difc-laws/data-protection-law-difc-law-no-5-2020)\n    (Dubai, Companies in Dubai International Financial Centre): Regulates the\n    processing of personal data in the DIFC free zone.\n\n    -\n    [PDPA](https://www.pdp.gov.my/jpdpv2/laws-of-malaysia-pdpa/personal-data-protection-act-2010/?lang=en)\n    (Malaysia, Commercial transactions): Personal Data Protection Act. Regulates\n    the processing of personal data in commercial transactions.\n\n    - [Privacy Act](https://www.ag.gov.au/rights-and-protections/privacy)\n    (Australia, Government agencies, and some private sector organizations)\n    regulates how personal information is handled by Australian government\n    agencies and some private sector organizations.\n\n    - [KVKK](https://www.kvkk.gov.tr/Icerik/6649/Personal-Data-Protection-Law)\n    (Turkey, All sectors): Turkish Personal Data Protection Law. Regulates the\n    processing of personal data and protects individual rights.\n\n\n    These standards reflect the growing global concern for data privacy and\n    security. Many countries are developing their own frameworks inspired by\n    established regulations like GDPR. Each standard is tailored to the specific\n    legal, cultural, and economic context of its country.\n\n\n    ### Industry-specific standards\n\n\n    - [PCI DSS](https://www.pcisecuritystandards.org/) (Financial Services): The\n    Payment Card Industry Data Security Standard applies to all organizations\n    that handle credit card information globally.\n\n    - [ISO 27001](https://www.iso.org/standard/iso-iec-27000-family) (All\n    industries) is an Information Security Management System standard that\n    provides a framework for information security management practices.\n\n    - [GAMP 5](https://qbdgroup.com/en/blog/gamp-categories/) (Pharmaceutical):\n    Good Automated Manufacturing Practice. Guidelines for computerized systems\n    in pharmaceutical manufacturing.\n\n    - [ISO 13485](https://www.iso.org/standard/59752.html) (Medical Devices):\n    Specifies requirements for a quality management system for medical device\n    manufacturers.\n\n    - [COBIT](https://www.isaca.org/resources/cobit) (IT Management): Control\n    Objectives for Information and Related Technologies. Framework for IT\n    management and IT governance.\n\n    - [ITIL](https://en.wikipedia.org/wiki/ITIL) (IT Services) is an Information\n    Technology Infrastructure Library, a set of detailed practices for IT\n    service management.\n\n    - [NIST CSF](https://www.nist.gov/cyberframework) (Cybersecurity): National\n    Institute of Standards and Technology Cybersecurity Framework. Guidance on\n    managing and reducing cybersecurity risk.\n\n    - [WCAG](https://www.w3.org/WAI/standards-guidelines/wcag/) (Web\n    Accessibility): The Web Content Accessibility Guidelines aim to make web\n    content more accessible to people with disabilities.\n\n    - [Basel III](https://www.bis.org/bcbs/basel3.htm) (Banking) is the\n    international regulatory framework for banks, including IT risk management\n    requirements.\n\n    - [TISAX](https://portal.enx.com/en-US/TISAX/) (Automotive): Trusted\n    Information Security Assessment Exchange. Information security assessment\n    and exchange mechanism for the automotive industry. (Learn how [GitLab's\n    TISAX\n    certification](https://about.gitlab.com/blog/gitlab-drives-automotive-industry-information-security-with-tisax/)\n    helps customers in the automotive industry.)\n\n\n    These standards apply across national boundaries to specific industries or\n    aspects of IT, ensuring consistent practices and security measures globally\n    within their respective domains.\n\n\n    ## Importance of continuous compliance\n\n    Organizations need to implement systems that ensure compliance with relevant\n    regulatory requirements and can achieve this with continuous compliance.\n    [Continuous software\n    compliance](https://about.gitlab.com/solutions/compliance/) is essential to\n    every industry, as it provides ongoing monitoring, assessment, and\n    adjustment of an organization's systems, processes, and practices to ensure\n    they consistently meet relevant standards and regulations.\n\n\n    Continuous compliance is not just a regulatory checkbox but a strategic\n    necessity for software development today. It empowers organizations to\n    proactively navigate emerging threats, technological shifts, and regulatory\n    changes while fostering stakeholder trust, operational efficiency, and\n    competitive advantage in an increasingly complex business environment.\n\n\n    ## Regulatory compliance vs. self-imposed standards\n\n\n    Regulatory compliance and self-imposed standards are two distinct approaches\n    to organizational governance. Regulatory compliance involves adhering to\n    mandatory laws and regulations set by external authorities, which have a\n    broad scope and potential legal consequences for non-compliance. It focuses\n    on meeting minimum legal requirements and is generally less flexible.\n    Examples include GDPR, HIPAA, and SOX.\n\n\n    In contrast, self-imposed standards are voluntary guidelines adopted by\n    organizations to improve quality, security, or performance. These can be\n    tailored to specific needs, are highly adaptable, and typically aim to\n    exceed minimum requirements. While failure to meet self-imposed standards\n    may impact reputation, it usually doesn't have legal ramifications.\n\n    The key differences lie in their origin, motivation, adaptability, and\n    scope. Many organizations implement both approaches to create a\n    comprehensive quality, security, and performance management strategy.\n\n\n    ## Compliance management\n\n\n    To meet standards, organizations must evaluate the right [compliance\n    metrics](https://advisory.kpmg.us/articles/2018/compliance-metrics.html) and\n    integrate them into their standard operating procedures to provide insights\n    that enable early detection and prevention of current and future compliance\n    risks. Thus, there is a need for efficient [compliance\n    management](https://about.gitlab.com/solutions/compliance/). Compliance\n    management goes beyond checking off a checklist periodically; it's a\n    comprehensive organization-wide continuous process.\n\n\n    ## Compliance management with GitLab\n\n\n    GitLab provides features that allow organizations to create [compliance\n    frameworks](https://docs.gitlab.com/user/group/compliance_frameworks/),\n    [security\n    policies](https://docs.gitlab.com/user/application_security/policies/),\n    and [audit\n    management](https://docs.gitlab.com/administration/audit_reports/).\n    GitLab also enables compliance or leadership teams to monitor compliance\n    metrics with [compliance\n    reports](https://docs.gitlab.com/user/compliance/compliance_report/).\n    Let's take a look at some of these features.\n\n\n    ### Compliance frameworks and pipelines\n\n\n    Organizations can create a [compliance\n    framework](https://docs.gitlab.com/user/group/compliance_frameworks/)\n    that identifies projects in GitLab that must meet defined compliance\n    requirements, which can be enforced with [compliance\n    pipelines](https://docs.gitlab.com/user/group/compliance_pipelines/).\n    For example, a FinTech company can create a [default compliance\n    framework](https://docs.gitlab.com/user/group/compliance_frameworks/#default-compliance-frameworks)\n    for all projects, ensuring every stage of their software development\n    lifecycle meets the PCI DSS requirements for handling cardholder data.\n\n\n    These requirements are then enforced by ensuring every change introduced to\n    the codebase is sufficiently tested automatically with GitLab's [application\n    security features](https://docs.gitlab.com/user/application_security/),\n    which cover source code, dependencies, licenses, vulnerabilities in running\n    application and infrastructure configurations. You can learn more about how\n    GitLab helps you achieve PCI compliance and other [regulatory\n    compliance](https://about.gitlab.com/solutions/software-compliance/) with\n    compliance frameworks.\n\n\n    The following videos demonstrate setting up and using compliance frameworks\n    and pipelines.\n\n\n    **Video tutorial: Create compliance frameworks**\n\n\n    \u003C!-- blank line -->\n\n    \u003Cfigure class=\"video_container\">\n      \u003Ciframe src=\"https://www.youtube.com/embed/IDswzRI-8VQ\" title=\"How to setup Compliance Frameworks & Pipelines in GitLab\" frameborder=\"0\" allowfullscreen=\"true\"> \u003C/iframe>\n    \u003C/figure>\n\n    \u003C!-- blank line -->\n\n\n    **Video tutorial: Enforce compliance pipelines**\n\n\n    \u003C!-- blank line -->\n\n    \u003Cfigure class=\"video_container\">\n      \u003Ciframe src=\"https://www.youtube.com/embed/jKA_e_jimoI\" title=\"GitLab Compliance Pipelines & Overriding Settings\" frameborder=\"0\" allowfullscreen=\"true\"> \u003C/iframe>\n    \u003C/figure>\n\n    \u003C!-- blank line -->\n\n\n    ### Security policy management\n\n\n    Security and compliance teams can use GitLab to enforce compliance\n    requirements by ensuring security scanners run in certain pipelines or\n    require approval on merge requests when [security\n    policies](https://docs.gitlab.com/user/application_security/policies/)\n    are violated. GitLab supports [scan\n    execution](https://docs.gitlab.com/user/application_security/policies/scan-execution-policies/)\n    and [scan\n    result](https://docs.gitlab.com/user/application_security/policies/scan-result-policies/)\n    policies. These policies are defined in a dedicated [security policy\n    project](https://docs.gitlab.com/user/application_security/policies/#security-policy-project)\n    that separates duties between security and development teams. Security\n    policies can be applied granularly at the group, sub-group, and project\n    levels. The policies can be edited in rule mode, which uses the [policy\n    editor](https://docs.gitlab.com/user/application_security/policies/#policy-editor),\n    or by yaml mode.\n\n\n    #### Scan execution policies\n\n    Scan execution policies can be configured to run on a specified [GitLab\n    Runner](https://docs.gitlab.com/runner/), including the following:\n\n    -  [Static Application Security\n    Testing](https://docs.gitlab.com/user/application_security/sast/)\n\n    - [Infrastructure as\n\n    Code](https://docs.gitlab.com/user/application_security/iac_scanning/)\n\n    - [Dynamic Application Security\n    Testing](https://docs.gitlab.com/user/application_security/dast/)\n\n    - [Secret\n    Detection](https://docs.gitlab.com/user/application_security/secret_detection/)\n\n    - [Container\n    Scanning](https://docs.gitlab.com/user/application_security/container_scanning/)\n\n    - [Dependency\n    Scanning](https://docs.gitlab.com/user/application_security/dependency_scanning/)\n\n\n    The scan jobs can be run on schedule or anytime a pipeline runs. Compliance\n    and security teams can use scan execution policies to periodically check on\n    and proactively prevent vulnerability escalation as part of a vulnerability\n    management strategy. They can also reinforce controls when new trends are\n    observed from scan results.\n\n\n    **Video tutorial: Set up security scan policies in GitLab**\n\n\n    \u003C!-- blank line -->\n\n    \u003Cfigure class=\"video_container\">\n      \u003Ciframe src=\"https://www.youtube.com/embed/ZBcqGmEwORA\" title=\"How to set up security scan policies in GitLab\" frameborder=\"0\" allowfullscreen=\"true\"> \u003C/iframe>\n    \u003C/figure>\n\n    \u003C!-- blank line -->\n\n\n    #### Scan result policies\n\n\n    Scan result policies add required review and approval for merge requests\n    when the results of specified security scans violate the policies' rules.\n    For example, a policy can require a security team member to take action when\n    a newly identified critical SAST vulnerability is detected. This way,\n    security and compliance team members can support developers while ensuring\n    the changes introduced to the codebase are secure and meet compliance\n    requirements.\n\n\n    **Video tutorial: Overview of GitLab Scan Result Policies**\n\n\n    \u003C!-- blank line -->\n\n    \u003Cfigure class=\"video_container\">\n      \u003Ciframe src=\"https://www.youtube.com/embed/w5I9gcUgr9U\" title=\"Overview of GitLab Scan Result Policies\" frameborder=\"0\" allowfullscreen=\"true\"> \u003C/iframe>\n    \u003C/figure>\n\n    \u003C!-- blank line -->\n\n\n    #### License approval policies\n\n    When selecting scan types for scan result policy rules, you can choose\n    between security scan, the default behavior for scan result policies, and\n    license scan, which helps ensure license compliance. License scanning\n    depends on the output of the [dependency\n    scanning](https://docs.gitlab.com/user/application_security/dependency_scanning/)\n    [CI/CD](https://about.gitlab.com/topics/ci-cd/) job to check if identified\n    licenses match specified criteria, then adds approval requirements before an\n    open merge request can be merged. This is crucial to ensure that only\n    dependencies with approved licenses are used in your organization.\n\n\n    **Video demo: License approval policies**\n\n\n    \u003C!-- blank line -->\n\n    \u003Cfigure class=\"video_container\">\n      \u003Ciframe src=\"https://www.youtube.com/embed/34qBQ9t8qO8\" title=\"License Approval Policies Demo\" frameborder=\"0\" allowfullscreen=\"true\"> \u003C/iframe>\n    \u003C/figure>\n\n    \u003C!-- blank line -->\n\n\n    ### Audit management\n\n    #### Preparing for audits\n\n    Audits are essential for compliance management because they allow you to\n    understand your organization's security and compliance posture. External\n    audits required by regulators are often detailed and exhaustive. To prepare\n    for them, organizations need to:\n\n    - Determine which regulations or standards will be assessed and what areas\n    of the organization will be examined.\n\n    - Analyze past audit results and ensure any previously identified issues\n    have been addressed.\n\n    - Collect all relevant policies, procedures, and records that demonstrate\n    compliance.\n\n    - Before the official audit, an internal audit must be performed to identify\n    and address any potential compliance gaps.\n\n    - Brief employees on the audit process and their roles. Conduct training if\n    necessary.\n\n    - Ensure all required documentation is easily accessible and well-organized.\n\n    - Ensure all compliance-related policies and procedures are up-to-date and\n    aligned with current regulations.\n\n    - Verify that all technical safeguards and controls are in place and\n    functioning correctly.\n\n    - Identify key personnel who may be interviewed and brief them on potential\n    questions.\n\n    - Address known issues: If any known compliance issues exist, develop and\n    document plans to address them.\n\n\n    To enable your preparedness, GitLab features: [Audit\n    Events](https://docs.gitlab.com/administration/audit_events/) and\n    [Compliance\n    Center](https://docs.gitlab.com/user/compliance/compliance_center/)\n    give a detailed view of an organization's compliance.\n\n\n    #### Using GitLab audit logs effectively\n\n\n    You want to know every action taken on the GitLab instance with [audit\n    events](https://docs.gitlab.com/administration/audit_events/). Audit\n    reports allow you to track every significant event, who performed it, and\n    when. You can also generate detailed reports from audit events using [audit\n    reports](https://docs.gitlab.com/administration/audit_reports/),\n    allowing you to prove your compliance to auditors or regulators.\n\n\n    ![Audit\n    events](https://res.cloudinary.com/about-gitlab-com/image/upload/v1750098755/Blog/Content%20Images/Blog/Content%20Images/image1_aHR0cHM6_1750098755493.png)\n\n\n    [The compliance\n    center](https://docs.gitlab.com/user/compliance/compliance_report/#compliance-violations-report)\n    is a significant component of audit management in GitLab, giving visibility\n    to your organization's compliance posture. Compliance reports detail every\n    violation discovered with the [compliance violations\n    report](https://docs.gitlab.com/user/compliance/compliance_center/compliance_violations_report/)\n    and the frameworks used by projects within your organization with the\n    compliance [frameworks\n    report](https://docs.gitlab.com/user/compliance/compliance_center/compliance_frameworks_report/).\n\n\n    ![Meet regulatory requirements - image\n    2](https://res.cloudinary.com/about-gitlab-com/image/upload/v1750098756/Blog/Content%20Images/Blog/Content%20Images/image2_aHR0cHM6_1750098755493.png)\n\n\n    \u003Ccenter>\u003Cem>Example of a compliance violations report from a parent GitLab group.\u003C/em>\u003C/center>\n\n\n    ![Meet regulatory requirements - image\n    3](https://res.cloudinary.com/about-gitlab-com/image/upload/v1750098755/Blog/Content%20Images/Blog/Content%20Images/image3_aHR0cHM6_1750098755495.png)\n\n\n    \u003Ccenter>\u003Cem>Example of a compliance framework report for all projects in a group\u003C/em>\u003C/center>\n\n\n    #### Audit events streaming\n\n    Most organizations have existing systems to monitor activities in their\n    systems in real-time. With [audit events\n    streaming](https://docs.gitlab.com/administration/audit_event_streaming/)\n    on GitLab, you can integrate third-party solutions like Splunk\n    infrastructure monitoring or DataDog streams monitoring service for\n    real-time audit events analytics. All audit events data are sent to the\n    streaming destination (it's essential to stream to a trusted service). Audit\n    events streaming can be [configured at top-level\n    groups](https://docs.gitlab.com/administration/audit_event_streaming/#top-level-group-streaming-destinations)\n    and at the [instance\n    level](https://docs.gitlab.com/administration/audit_event_streaming/#instance-streaming-destinations)\n    for self-managed GitLab instances.\n\n\n    ## Best practices for compliance management\n\n\n    Here are some best practices for effective compliance management:\n\n    - Establish a strong compliance culture that promotes organizational\n    compliance awareness and ensures leadership commitment and support.\n\n    - Develop a comprehensive compliance program with clear policies and\n    procedures and regularly review the program to reflect regulation changes.\n\n    - Implement risk assessment and management to regularly identify and assess\n    compliance risks, prioritizing risks based on potential impact and\n    likelihood.\n\n    - Conduct regular compliance training tailored to specific roles and\n    responsibilities for all employees.\n\n    - Implement compliance management to automate compliance monitoring and\n    compliance reporting where possible.\n\n    - Perform internal audits to identify gaps and areas for improvement. It is\n    also essential to consider external audits unbiasedly and use audit results\n    to refine and improve compliance processes.\n\n    - Stay informed about regulatory changes by assigning responsibility for\n    monitoring regulatory updates and participating in industry associations and\n    forums.\n\n    - Integrate compliance into business processes, embed compliance checks into\n    operational workflows, and consider compliance implications in strategic\n    decision-making. Align compliance goals with business objectives\n\n    - Develop response plans for potential compliance breaches and conduct mock\n    scenarios to test readiness for incidents and violations.\n\n\n    ## Learn more\n\n    Compliance is a continuous process of efficiently managing risk by\n    implementing guardrails and monitoring compliance metrics. GitLab empowers\n    organizations to fulfill regulatory standards with our [compliance\n    management](https://about.gitlab.com/solutions/compliance/) features. With\n    GitLab, you can improve the software supply chain experience, build more\n    secure software faster, and maintain the trust of your users, clients, and\n    community.\n\n\n    > Learn more about compliance and security policy management with the\n    [GitLab DevSecOps\n    tutorial](https://gitlab-da.gitlab.io/tutorials/security-and-governance/devsecops/simply-vulnerable-notes/),\n    which contains lessons covering the complete application security lifecycle\n    in GitLab.\n\n\n    ## Read more\n\n    - [Introducing GitLab Dedicated for\n    Government](https://about.gitlab.com/blog/introducing-gitlab-dedicated-for-government/)\n\n    - [How to ensure separation of duties and enforce compliance with\n    GitLab](https://about.gitlab.com/blog/ensuring-compliance/)\n\n    - [The ultimate guide to least privilege access with\n    GitLab](https://about.gitlab.com/blog/the-ultimate-guide-to-least-privilege-access-with-gitlab/)\n  category: security\n  tags:\n    - DevSecOps\n    - DevSecOps platform\n    - security\n    - public sector\n  updatedDate: '2024-08-22'\nconfig:\n  slug: meet-regulatory-standards-with-gitlab\n  featured: false\n  template: BlogPost\n",{"title":5,"description":17,"ogTitle":5,"ogDescription":17,"noIndex":14,"ogImage":19,"ogUrl":33,"ogSiteName":34,"ogType":35,"canonicalUrls":33},"https://about.gitlab.com/blog/meet-regulatory-standards-with-gitlab","https://about.gitlab.com","article","en-us/blog/meet-regulatory-standards-with-gitlab",[38,39,11,40],"devsecops","devsecops-platform","public-sector",[22,23,11,24],"NYQt2lGFTd8qHihzN7o2ghS_mZDx1lLmyZTHr6a545s",{"data":44},{"logo":45,"freeTrial":50,"sales":55,"login":60,"items":65,"search":373,"minimal":404,"duo":423,"switchNav":432,"pricingDeployment":443},{"config":46},{"href":47,"dataGaName":48,"dataGaLocation":49},"/","gitlab logo","header",{"text":51,"config":52},"Get free trial",{"href":53,"dataGaName":54,"dataGaLocation":49},"https://gitlab.com/-/trial_registrations/new?glm_source=about.gitlab.com&glm_content=default-saas-trial/","free trial",{"text":56,"config":57},"Talk to sales",{"href":58,"dataGaName":59,"dataGaLocation":49},"/sales/","sales",{"text":61,"config":62},"Sign in",{"href":63,"dataGaName":64,"dataGaLocation":49},"https://gitlab.com/users/sign_in/","sign in",[66,93,187,192,294,354],{"text":67,"config":68,"cards":70},"Platform",{"dataNavLevelOne":69},"platform",[71,77,85],{"title":67,"description":72,"link":73},"The intelligent orchestration platform for DevSecOps",{"text":74,"config":75},"Explore our Platform",{"href":76,"dataGaName":69,"dataGaLocation":49},"/platform/",{"title":78,"description":79,"link":80},"GitLab Duo Agent Platform","Agentic AI for the entire software lifecycle",{"text":81,"config":82},"Meet GitLab Duo",{"href":83,"dataGaName":84,"dataGaLocation":49},"/gitlab-duo-agent-platform/","gitlab duo agent platform",{"title":86,"description":87,"link":88},"Why GitLab","See the top reasons enterprises choose GitLab",{"text":89,"config":90},"Learn more",{"href":91,"dataGaName":92,"dataGaLocation":49},"/why-gitlab/","why gitlab",{"text":94,"left":29,"config":95,"link":97,"lists":101,"footer":170},"Product",{"dataNavLevelOne":96},"solutions",{"text":98,"config":99},"View all Solutions",{"href":100,"dataGaName":96,"dataGaLocation":49},"/solutions/",[102,126,149],{"title":103,"description":104,"link":105,"items":110},"Automation","CI/CD and automation to accelerate deployment",{"config":106},{"icon":107,"href":108,"dataGaName":109,"dataGaLocation":49},"AutomatedCodeAlt","/solutions/delivery-automation/","automated software delivery",[111,115,118,122],{"text":112,"config":113},"CI/CD",{"href":114,"dataGaLocation":49,"dataGaName":112},"/solutions/continuous-integration/",{"text":78,"config":116},{"href":83,"dataGaLocation":49,"dataGaName":117},"gitlab duo agent platform - product menu",{"text":119,"config":120},"Source Code Management",{"href":121,"dataGaLocation":49,"dataGaName":119},"/solutions/source-code-management/",{"text":123,"config":124},"Automated Software Delivery",{"href":108,"dataGaLocation":49,"dataGaName":125},"Automated software delivery",{"title":127,"description":128,"link":129,"items":134},"Security","Deliver code faster without compromising security",{"config":130},{"href":131,"dataGaName":132,"dataGaLocation":49,"icon":133},"/solutions/application-security-testing/","security and compliance","ShieldCheckLight",[135,139,144],{"text":136,"config":137},"Application Security Testing",{"href":131,"dataGaName":138,"dataGaLocation":49},"Application security testing",{"text":140,"config":141},"Software Supply Chain Security",{"href":142,"dataGaLocation":49,"dataGaName":143},"/solutions/supply-chain/","Software supply chain security",{"text":145,"config":146},"Software Compliance",{"href":147,"dataGaName":148,"dataGaLocation":49},"/solutions/software-compliance/","software compliance",{"title":150,"link":151,"items":156},"Measurement",{"config":152},{"icon":153,"href":154,"dataGaName":155,"dataGaLocation":49},"DigitalTransformation","/solutions/visibility-measurement/","visibility and measurement",[157,161,165],{"text":158,"config":159},"Visibility & Measurement",{"href":154,"dataGaLocation":49,"dataGaName":160},"Visibility and Measurement",{"text":162,"config":163},"Value Stream Management",{"href":164,"dataGaLocation":49,"dataGaName":162},"/solutions/value-stream-management/",{"text":166,"config":167},"Analytics & Insights",{"href":168,"dataGaLocation":49,"dataGaName":169},"/solutions/analytics-and-insights/","Analytics and insights",{"title":171,"items":172},"GitLab for",[173,178,183],{"text":174,"config":175},"Enterprise",{"href":176,"dataGaLocation":49,"dataGaName":177},"/enterprise/","enterprise",{"text":179,"config":180},"Small Business",{"href":181,"dataGaLocation":49,"dataGaName":182},"/small-business/","small business",{"text":184,"config":185},"Public Sector",{"href":186,"dataGaLocation":49,"dataGaName":24},"/solutions/public-sector/",{"text":188,"config":189},"Pricing",{"href":190,"dataGaName":191,"dataGaLocation":49,"dataNavLevelOne":191},"/pricing/","pricing",{"text":193,"config":194,"link":196,"lists":200,"feature":285},"Resources",{"dataNavLevelOne":195},"resources",{"text":197,"config":198},"View all resources",{"href":199,"dataGaName":195,"dataGaLocation":49},"/resources/",[201,234,257],{"title":202,"items":203},"Getting started",[204,209,214,219,224,229],{"text":205,"config":206},"Install",{"href":207,"dataGaName":208,"dataGaLocation":49},"/install/","install",{"text":210,"config":211},"Quick start guides",{"href":212,"dataGaName":213,"dataGaLocation":49},"/get-started/","quick setup checklists",{"text":215,"config":216},"Learn",{"href":217,"dataGaLocation":49,"dataGaName":218},"https://university.gitlab.com/","learn",{"text":220,"config":221},"Product documentation",{"href":222,"dataGaName":223,"dataGaLocation":49},"https://docs.gitlab.com/","product documentation",{"text":225,"config":226},"Best practice videos",{"href":227,"dataGaName":228,"dataGaLocation":49},"/getting-started-videos/","best practice videos",{"text":230,"config":231},"Integrations",{"href":232,"dataGaName":233,"dataGaLocation":49},"/integrations/","integrations",{"title":235,"items":236},"Discover",[237,242,247,252],{"text":238,"config":239},"Customer success stories",{"href":240,"dataGaName":241,"dataGaLocation":49},"/customers/","customer success stories",{"text":243,"config":244},"Blog",{"href":245,"dataGaName":246,"dataGaLocation":49},"/blog/","blog",{"text":248,"config":249},"The Source",{"href":250,"dataGaName":251,"dataGaLocation":49},"/the-source/","the source",{"text":253,"config":254},"Remote",{"href":255,"dataGaName":256,"dataGaLocation":49},"https://handbook.gitlab.com/handbook/company/culture/all-remote/","remote",{"title":258,"items":259},"Connect",[260,265,270,275,280],{"text":261,"config":262},"GitLab Services",{"href":263,"dataGaName":264,"dataGaLocation":49},"/services/","services",{"text":266,"config":267},"Community",{"href":268,"dataGaName":269,"dataGaLocation":49},"/community/","community",{"text":271,"config":272},"Forum",{"href":273,"dataGaName":274,"dataGaLocation":49},"https://forum.gitlab.com/","forum",{"text":276,"config":277},"Events",{"href":278,"dataGaName":279,"dataGaLocation":49},"/events/","events",{"text":281,"config":282},"Partners",{"href":283,"dataGaName":284,"dataGaLocation":49},"/partners/","partners",{"textColor":286,"title":287,"text":288,"link":289},"#000","What’s new in GitLab","Stay updated with our latest features and improvements.",{"text":290,"config":291},"Read the latest",{"href":292,"dataGaName":293,"dataGaLocation":49},"/releases/whats-new/","whats new",{"text":295,"config":296,"lists":298},"Company",{"dataNavLevelOne":297},"company",[299],{"items":300},[301,306,312,314,319,324,329,334,339,344,349],{"text":302,"config":303},"About",{"href":304,"dataGaName":305,"dataGaLocation":49},"/company/","about",{"text":307,"config":308,"footerGa":311},"Jobs",{"href":309,"dataGaName":310,"dataGaLocation":49},"/jobs/","jobs",{"dataGaName":310},{"text":276,"config":313},{"href":278,"dataGaName":279,"dataGaLocation":49},{"text":315,"config":316},"Leadership",{"href":317,"dataGaName":318,"dataGaLocation":49},"/company/team/e-group/","leadership",{"text":320,"config":321},"Team",{"href":322,"dataGaName":323,"dataGaLocation":49},"/company/team/","team",{"text":325,"config":326},"Handbook",{"href":327,"dataGaName":328,"dataGaLocation":49},"https://handbook.gitlab.com/","handbook",{"text":330,"config":331},"Investor relations",{"href":332,"dataGaName":333,"dataGaLocation":49},"https://ir.gitlab.com/","investor relations",{"text":335,"config":336},"Trust Center",{"href":337,"dataGaName":338,"dataGaLocation":49},"/security/","trust center",{"text":340,"config":341},"AI Transparency Center",{"href":342,"dataGaName":343,"dataGaLocation":49},"/ai-transparency-center/","ai transparency center",{"text":345,"config":346},"Newsletter",{"href":347,"dataGaName":348,"dataGaLocation":49},"/company/contact/#contact-forms","newsletter",{"text":350,"config":351},"Press",{"href":352,"dataGaName":353,"dataGaLocation":49},"/press/","press",{"text":355,"config":356,"lists":357},"Contact us",{"dataNavLevelOne":297},[358],{"items":359},[360,363,368],{"text":56,"config":361},{"href":58,"dataGaName":362,"dataGaLocation":49},"talk to sales",{"text":364,"config":365},"Support portal",{"href":366,"dataGaName":367,"dataGaLocation":49},"https://support.gitlab.com","support portal",{"text":369,"config":370},"Customer portal",{"href":371,"dataGaName":372,"dataGaLocation":49},"https://customers.gitlab.com/customers/sign_in/","customer portal",{"close":374,"login":375,"suggestions":382},"Close",{"text":376,"link":377},"To search repositories and projects, login to",{"text":378,"config":379},"gitlab.com",{"href":63,"dataGaName":380,"dataGaLocation":381},"search login","search",{"text":383,"default":384},"Suggestions",[385,387,391,393,397,401],{"text":78,"config":386},{"href":83,"dataGaName":78,"dataGaLocation":381},{"text":388,"config":389},"Code Suggestions (AI)",{"href":390,"dataGaName":388,"dataGaLocation":381},"/solutions/code-suggestions/",{"text":112,"config":392},{"href":114,"dataGaName":112,"dataGaLocation":381},{"text":394,"config":395},"GitLab on AWS",{"href":396,"dataGaName":394,"dataGaLocation":381},"/partners/technology-partners/aws/",{"text":398,"config":399},"GitLab on Google Cloud",{"href":400,"dataGaName":398,"dataGaLocation":381},"/partners/technology-partners/google-cloud-platform/",{"text":402,"config":403},"Why GitLab?",{"href":91,"dataGaName":402,"dataGaLocation":381},{"freeTrial":405,"mobileIcon":410,"desktopIcon":415,"secondaryButton":418},{"text":406,"config":407},"Start free trial",{"href":408,"dataGaName":54,"dataGaLocation":409},"https://gitlab.com/-/trials/new/","nav",{"altText":411,"config":412},"Gitlab Icon",{"src":413,"dataGaName":414,"dataGaLocation":409},"https://res.cloudinary.com/about-gitlab-com/image/upload/v1758203874/jypbw1jx72aexsoohd7x.svg","gitlab icon",{"altText":411,"config":416},{"src":417,"dataGaName":414,"dataGaLocation":409},"https://res.cloudinary.com/about-gitlab-com/image/upload/v1758203875/gs4c8p8opsgvflgkswz9.svg",{"text":419,"config":420},"Get Started",{"href":421,"dataGaName":422,"dataGaLocation":409},"https://gitlab.com/-/trial_registrations/new?glm_source=about.gitlab.com/get-started/","get started",{"freeTrial":424,"mobileIcon":428,"desktopIcon":430},{"text":425,"config":426},"Learn more about GitLab Duo",{"href":83,"dataGaName":427,"dataGaLocation":409},"gitlab duo",{"altText":411,"config":429},{"src":413,"dataGaName":414,"dataGaLocation":409},{"altText":411,"config":431},{"src":417,"dataGaName":414,"dataGaLocation":409},{"button":433,"mobileIcon":438,"desktopIcon":440},{"text":434,"config":435},"/switch",{"href":436,"dataGaName":437,"dataGaLocation":409},"#contact","switch",{"altText":411,"config":439},{"src":413,"dataGaName":414,"dataGaLocation":409},{"altText":411,"config":441},{"src":442,"dataGaName":414,"dataGaLocation":409},"https://res.cloudinary.com/about-gitlab-com/image/upload/v1773335277/ohhpiuoxoldryzrnhfrh.png",{"freeTrial":444,"mobileIcon":449,"desktopIcon":451},{"text":445,"config":446},"Back to pricing",{"href":190,"dataGaName":447,"dataGaLocation":409,"icon":448},"back to pricing","GoBack",{"altText":411,"config":450},{"src":413,"dataGaName":414,"dataGaLocation":409},{"altText":411,"config":452},{"src":417,"dataGaName":414,"dataGaLocation":409},{"title":454,"button":455,"config":460},"See how agentic AI transforms software delivery",{"text":456,"config":457},"Watch GitLab Transcend now",{"href":458,"dataGaName":459,"dataGaLocation":49},"/events/transcend/virtual/","transcend event",{"layout":461,"icon":462,"disabled":29},"release","AiStar",{"data":464},{"text":465,"source":466,"edit":472,"contribute":477,"config":482,"items":487,"minimal":691},"Git is a trademark of Software Freedom Conservancy and our use of 'GitLab' is under license",{"text":467,"config":468},"View page source",{"href":469,"dataGaName":470,"dataGaLocation":471},"https://gitlab.com/gitlab-com/marketing/digital-experience/about-gitlab-com/","page source","footer",{"text":473,"config":474},"Edit this page",{"href":475,"dataGaName":476,"dataGaLocation":471},"https://gitlab.com/gitlab-com/marketing/digital-experience/about-gitlab-com/-/blob/main/content/","web ide",{"text":478,"config":479},"Please contribute",{"href":480,"dataGaName":481,"dataGaLocation":471},"https://gitlab.com/gitlab-com/marketing/digital-experience/about-gitlab-com/-/blob/main/CONTRIBUTING.md/","please contribute",{"twitter":483,"facebook":484,"youtube":485,"linkedin":486},"https://twitter.com/gitlab","https://www.facebook.com/gitlab","https://www.youtube.com/channel/UCnMGQ8QHMAnVIsI3xJrihhg","https://www.linkedin.com/company/gitlab-com",[488,535,586,630,657],{"title":188,"links":489,"subMenu":504},[490,494,499],{"text":491,"config":492},"View plans",{"href":190,"dataGaName":493,"dataGaLocation":471},"view plans",{"text":495,"config":496},"Why Premium?",{"href":497,"dataGaName":498,"dataGaLocation":471},"/pricing/premium/","why premium",{"text":500,"config":501},"Why Ultimate?",{"href":502,"dataGaName":503,"dataGaLocation":471},"/pricing/ultimate/","why ultimate",[505],{"title":506,"links":507},"Contact Us",[508,511,513,515,520,525,530],{"text":509,"config":510},"Contact sales",{"href":58,"dataGaName":59,"dataGaLocation":471},{"text":364,"config":512},{"href":366,"dataGaName":367,"dataGaLocation":471},{"text":369,"config":514},{"href":371,"dataGaName":372,"dataGaLocation":471},{"text":516,"config":517},"Status",{"href":518,"dataGaName":519,"dataGaLocation":471},"https://status.gitlab.com/","status",{"text":521,"config":522},"Terms of use",{"href":523,"dataGaName":524,"dataGaLocation":471},"/terms/","terms of use",{"text":526,"config":527},"Privacy statement",{"href":528,"dataGaName":529,"dataGaLocation":471},"/privacy/","privacy statement",{"text":531,"config":532},"Cookie preferences",{"dataGaName":533,"dataGaLocation":471,"id":534,"isOneTrustButton":29},"cookie preferences","ot-sdk-btn",{"title":94,"links":536,"subMenu":544},[537,540],{"text":23,"config":538},{"href":76,"dataGaName":539,"dataGaLocation":471},"devsecops platform",{"text":541,"config":542},"AI-Assisted Development",{"href":83,"dataGaName":543,"dataGaLocation":471},"ai-assisted development",[545],{"title":546,"links":547},"Topics",[548,553,558,563,568,571,576,581],{"text":549,"config":550},"CICD",{"href":551,"dataGaName":552,"dataGaLocation":471},"/topics/ci-cd/","cicd",{"text":554,"config":555},"GitOps",{"href":556,"dataGaName":557,"dataGaLocation":471},"/topics/gitops/","gitops",{"text":559,"config":560},"DevOps",{"href":561,"dataGaName":562,"dataGaLocation":471},"/topics/devops/","devops",{"text":564,"config":565},"Version Control",{"href":566,"dataGaName":567,"dataGaLocation":471},"/topics/version-control/","version control",{"text":22,"config":569},{"href":570,"dataGaName":38,"dataGaLocation":471},"/topics/devsecops/",{"text":572,"config":573},"Cloud Native",{"href":574,"dataGaName":575,"dataGaLocation":471},"/topics/cloud-native/","cloud native",{"text":577,"config":578},"AI for Coding",{"href":579,"dataGaName":580,"dataGaLocation":471},"/topics/devops/ai-for-coding/","ai for coding",{"text":582,"config":583},"Agentic AI",{"href":584,"dataGaName":585,"dataGaLocation":471},"/topics/agentic-ai/","agentic ai",{"title":587,"links":588},"Solutions",[589,591,593,598,602,605,609,612,614,617,620,625],{"text":136,"config":590},{"href":131,"dataGaName":136,"dataGaLocation":471},{"text":125,"config":592},{"href":108,"dataGaName":109,"dataGaLocation":471},{"text":594,"config":595},"Agile development",{"href":596,"dataGaName":597,"dataGaLocation":471},"/solutions/agile-delivery/","agile delivery",{"text":599,"config":600},"SCM",{"href":121,"dataGaName":601,"dataGaLocation":471},"source code management",{"text":549,"config":603},{"href":114,"dataGaName":604,"dataGaLocation":471},"continuous integration & delivery",{"text":606,"config":607},"Value stream management",{"href":164,"dataGaName":608,"dataGaLocation":471},"value stream management",{"text":554,"config":610},{"href":611,"dataGaName":557,"dataGaLocation":471},"/solutions/gitops/",{"text":174,"config":613},{"href":176,"dataGaName":177,"dataGaLocation":471},{"text":615,"config":616},"Small business",{"href":181,"dataGaName":182,"dataGaLocation":471},{"text":618,"config":619},"Public sector",{"href":186,"dataGaName":24,"dataGaLocation":471},{"text":621,"config":622},"Education",{"href":623,"dataGaName":624,"dataGaLocation":471},"/solutions/education/","education",{"text":626,"config":627},"Financial services",{"href":628,"dataGaName":629,"dataGaLocation":471},"/solutions/finance/","financial services",{"title":193,"links":631},[632,634,636,638,641,643,645,647,649,651,653,655],{"text":205,"config":633},{"href":207,"dataGaName":208,"dataGaLocation":471},{"text":210,"config":635},{"href":212,"dataGaName":213,"dataGaLocation":471},{"text":215,"config":637},{"href":217,"dataGaName":218,"dataGaLocation":471},{"text":220,"config":639},{"href":222,"dataGaName":640,"dataGaLocation":471},"docs",{"text":243,"config":642},{"href":245,"dataGaName":246,"dataGaLocation":471},{"text":238,"config":644},{"href":240,"dataGaName":241,"dataGaLocation":471},{"text":253,"config":646},{"href":255,"dataGaName":256,"dataGaLocation":471},{"text":261,"config":648},{"href":263,"dataGaName":264,"dataGaLocation":471},{"text":266,"config":650},{"href":268,"dataGaName":269,"dataGaLocation":471},{"text":271,"config":652},{"href":273,"dataGaName":274,"dataGaLocation":471},{"text":276,"config":654},{"href":278,"dataGaName":279,"dataGaLocation":471},{"text":281,"config":656},{"href":283,"dataGaName":284,"dataGaLocation":471},{"title":295,"links":658},[659,661,663,665,667,669,671,675,680,682,684,686],{"text":302,"config":660},{"href":304,"dataGaName":297,"dataGaLocation":471},{"text":307,"config":662},{"href":309,"dataGaName":310,"dataGaLocation":471},{"text":315,"config":664},{"href":317,"dataGaName":318,"dataGaLocation":471},{"text":320,"config":666},{"href":322,"dataGaName":323,"dataGaLocation":471},{"text":325,"config":668},{"href":327,"dataGaName":328,"dataGaLocation":471},{"text":330,"config":670},{"href":332,"dataGaName":333,"dataGaLocation":471},{"text":672,"config":673},"Sustainability",{"href":674,"dataGaName":672,"dataGaLocation":471},"/sustainability/",{"text":676,"config":677},"Diversity, inclusion and belonging (DIB)",{"href":678,"dataGaName":679,"dataGaLocation":471},"/diversity-inclusion-belonging/","Diversity, inclusion and belonging",{"text":335,"config":681},{"href":337,"dataGaName":338,"dataGaLocation":471},{"text":345,"config":683},{"href":347,"dataGaName":348,"dataGaLocation":471},{"text":350,"config":685},{"href":352,"dataGaName":353,"dataGaLocation":471},{"text":687,"config":688},"Modern Slavery Transparency Statement",{"href":689,"dataGaName":690,"dataGaLocation":471},"https://handbook.gitlab.com/handbook/legal/modern-slavery-act-transparency-statement/","modern slavery transparency statement",{"items":692},[693,696,699],{"text":694,"config":695},"Terms",{"href":523,"dataGaName":524,"dataGaLocation":471},{"text":697,"config":698},"Cookies",{"dataGaName":533,"dataGaLocation":471,"id":534,"isOneTrustButton":29},{"text":700,"config":701},"Privacy",{"href":528,"dataGaName":529,"dataGaLocation":471},[703],{"id":704,"title":9,"body":27,"config":705,"content":707,"description":27,"extension":26,"meta":711,"navigation":29,"path":712,"seo":713,"stem":714,"__hash__":715},"blogAuthors/en-us/blog/authors/abubakar-siddiq-ango.yml",{"template":706},"BlogAuthor",{"name":9,"config":708},{"headshot":709,"ctfId":710},"https://res.cloudinary.com/about-gitlab-com/image/upload/v1749660104/Blog/Author%20Headshots/abuango-headshot.jpg","abuango",{},"/en-us/blog/authors/abubakar-siddiq-ango",{},"en-us/blog/authors/abubakar-siddiq-ango","u5Jv4JxCpfmcGQuXEU4Lr5xVBJP9LAB2NkXRMLeYwPE",[717,730,745],{"content":718,"config":728},{"title":719,"description":720,"authors":721,"date":723,"body":724,"category":11,"tags":725,"heroImage":727},"Prepare your pipeline for AI-discovered zero-days","AI is finding vulnerabilities faster than teams can patch. Learn how pipeline enforcement, automated triage, and AI remediation close the gap.",[722],"Omer Azaria","2026-04-20","Anthropic's [Mythos Preview model](https://red.anthropic.com/2026/mythos-preview/) recently identified thousands of zero-day vulnerabilities across every major operating system and web browser, including an OpenBSD bug that went undetected for 27 years. In testing, Mythos autonomously chained four vulnerabilities into a working browser exploit that escaped its sandbox. Anthropic is restricting access to Mythos, but the company’s head of offensive cyber research expects threats to have comparable tooling within six to twelve months.\n\nThe defender side of the equation hasn't kept pace. One third of exploited Common Vulnerabilities and Exposures (CVEs) in the first half of 2025 showed activity on or before disclosure day, before most teams even know there's something to patch. AI is compressing that window further, accelerating attackers and flooding teams with whitehat disclosures faster than they can triage. Defender tooling has improved, but most organizations can't operationalize it fast enough to close the gap between discovery and exploitation.\n\nWhen the window between disclosure and exploitation is measured in hours, the security team can't be the last line of defense. Security has to run where code enters the system: in the pipeline, on every merge request, enforced by policy. The fixes that can be automated should be. The ones that can't need to reach the right human faster than they do today.\n\n## Known vulnerabilities are already outpacing remediation\n\nThe bottleneck isn't detection, it's acting at scale on what teams already know. Sixty percent of breaches in the 2025 Verizon DBIR involved exploiting known vulnerabilities where a patch was already available. Teams couldn’t close them in time.\n\nThe backlog was untenable before Mythos. Developers spend [11 hours per month remediating vulnerabilities](https://about.gitlab.com/resources/developer-survey/) post-release instead of shipping new work. Over half of organizations have at least one open internet-facing vulnerability, and the median time to close half of those is 361 days. Exploitation takes hours, while remediation takes months.\n\nAI-assisted development is widening the gap, and stakeholders know it. By June 2025, AI-generated code was adding over 10,000 new security findings per month across Fortune 50 repositories, a 10x jump from six months earlier. Georgia Tech identified 34 [CVEs attributable to AI-generated code](https://research.gatech.edu/bad-vibes-ai-generated-code-vulnerable-researchers-warn) in March 2026, up from 6 in January, and that count reflects only the ones where AI authorship is clear. AI coding assistants hallucinate package names, reach for outdated patterns, and copy insecure examples from training data. More code, more dependencies, and more vulnerabilities per line are generated faster than security teams can review them.\n\nDefenders need to harness frontier AI models, too — not bolted onto the SDLC as external tooling, but running inside the same policies, approvals, and audit trail as the rest of the team. \n\n## Security at the speed of AI coding\n\nWhen a critical CVE drops, how quickly can your team confirm which projects are affected? How many tools does an alert cross before a developer can submit a fix?\n\nThe teams that benefit most from AI already have policies, enforcement, and controls embedded in their development workflows. AI amplifies that foundation. It doesn't replace it.\n\n**Enforcement at the point of change.** As exploitation windows compress, every line of code entering a repository needs to pass through a defined set of controls. Not a separate review, in a different tool, by a different team. Organizations need the ability to enforce security policies across every group and project, with the merge request as the enforcement point. Policies defined once, applied everywhere, with exceptions reviewed, approved, and logged.\n\n**Simple issues caught before the merge request, not during.** Hardcoded secrets, known-vulnerable imports, and deprecated API calls can be flagged in the IDE before a developer pushes a commit. Catching them at authoring time means fewer findings blocking the MR, so review cycles go to the findings that require cross-component context: reachability, exploitability, and architectural risk.\n\n**Triage automated by default, not by exception.** Embedding security into every merge request creates a volume problem. More scans, more findings, more noise reaching developers who aren’t trained to distinguish a reachable critical from a theoretical one. AI must handle false positive detection, reachability, exploitability context, and severity assessment before a developer sees the finding, so the findings they see actually warrant their time.\n\n**Remediation governed like any other change.** AI-based remediation compresses the timeline for closing vulnerabilities, but every generated fix must move through the same governance as a human-authored change: policies enforce scans, the right reviewers approve, and evidence is recorded. GitLab’s automated remediation capability proposes each fix in a merge request with a confidence score. The MR records which policy applied, which scans ran, what they found, and who approved. Human code and AI-generated code move through the same process, with the same audit trail.\n\n## What a ready pipeline looks like\n\nHere's how these pieces work together when a high-severity vulnerability is discovered and the clock is running.\n\nA proof-of-concept exploit for a vulnerability in a popular open-source package appears on a security mailing list. There’s no CVE, no National Vulnerability Database (NVD) entry, and no scanner signature yet. The security team finds out the usual way: someone shares it in Slack.\n\nA security engineer asks the security agent if the package is in use, which projects have affected versions, and whether any vulnerable call paths are reachable in production. The agent checks the dependency graph for every project, matches the affected versions and entry points from the disclosure, and returns a ranked list of exposed projects with details about reachability. There’s no need to search through repositories by hand or wait for a scanner update. The question, \"Are we exposed?\" is answered in minutes.\n\nThe engineer starts a remediation campaign for every exposed project. The remediation agent suggests fixes: version updates where a patched release is available, and targeted call-path patches where it is not. Scan execution policies are already in place for projects tagged SOC 2. The engineer hardens the rules to block merges on any merge request that introduces or keeps the affected dependency, and an approval policy now requires security sign-off on every fix. The agent's first proposed patch fails the pipeline when an integration test catches a regression. The agent revises the patch based on the test failure, and the second attempt passes. Developers review the changes, security signs off under the stricter policy, and merges proceed across the campaign.\n\nAt the next audit review, the security team presents a report showing how policies were enforced and risks were reduced during the campaign. It includes scan results, policies applied, approvers, and merge timestamps for every MR in every affected project. The evidence was automatically generated in flight, not assembled after the fact.\n\n## Close the gaps now\n\nMythos exists today, and comparable models will be in attacker hands within a year. Every month between now and then is a chance to strengthen your software supply chain.\n\nAsk these questions about your pipeline:\n\n* How do you enforce that security scans run on every merge request, not just the projects where teams configured them?\n\n* If a compromised package entered your dependency tree today, would your pipeline catch it before build?\n\n* When a scanner flags a critical finding, how many tool boundaries does it cross before a developer starts the fix?\n\n* If an AI agent proposed a code fix for a vulnerability, what process would that fix go through before reaching production, and is that process auditable?\n\n* When auditors ask for evidence that a specific policy was enforced on a specific change, how long does it take to produce?\n\nIf the answers expose gaps, address them now. [Talk to a GitLab solutions architect](https://about.gitlab.com/sales/) about the role of security governance in your development lifecycle.",[726,11,23],"AI/ML","https://res.cloudinary.com/about-gitlab-com/image/upload/v1772195014/ooezwusxjl1f7ijfmbvj.png",{"featured":29,"template":15,"slug":729},"prepare-your-pipeline-for-ai-discovered-zero-days",{"content":731,"config":743},{"title":732,"description":733,"authors":734,"heroImage":736,"date":737,"category":11,"tags":738,"body":742},"Manage vulnerability noise at scale with auto-dismiss policies","Learn how to cut through scanner noise and focus on the vulnerabilities that matter most with GitLab security, including use cases and templates.",[735],"Grant Hickman","https://res.cloudinary.com/about-gitlab-com/image/upload/v1774375772/kpaaaiqhokevxxeoxvu0.png","2026-03-25",[11,739,22,740,741],"tutorial","features","product","Security scanners are essential, but not every finding requires action. Test code, vendored dependencies, generated files, and known false positives create noise that buries the vulnerabilities that actually matter. Security teams waste hours manually dismissing the same irrelevant findings across projects and pipelines. They experience slower triage, alert fatigue, and developer friction that undermines adoption of security scanning itself.\n\nGitLab's auto-dismiss vulnerability policies let you codify your triage decisions once and apply them automatically on every default-branch pipeline. Define criteria based on file path, directory, or vulnerability identifier (CVE, CWE), choose a dismissal reason, and let GitLab handle the rest.\n\n## Why auto-dismiss?\nAuto-dismiss vulnerability policies enable security teams to:\n- **Eliminate triage noise**: Automatically dismiss findings in test code, vendored dependencies, and generated files.\n- **Enforce decisions at scale**: Apply policies centrally to dismiss known false positives across your entire organization.\n- **Maintain audit transparency**: Every auto-dismissed finding includes a documented reason and links back to the policy that triggered it.\n- **Preserve the record**: Unlike scanner exclusions, dismissed vulnerabilities remain in your report, so you can revisit decisions if conditions change.\n\n## How auto-dismiss policies work\n\n1. **Define your policy** in a vulnerability management policy YAML file. Specify match criteria (file path, directory, or identifier) and a dismissal reason.\n\n2. **Merge and activate.** Create the policy via **Secure > Policies > New  policy > Vulnerability management policy**. Merge the MR to enable it.\n3. **Run your pipeline.** On every default-branch pipeline, matching vulnerabilities are automatically set to \"Dismissed\" with the specified reason. Up to 1,000 vulnerabilities are processed per run.\n4. **Measure the impact.** Filter your vulnerability report by status \"Dismissed\" to see exactly what was cleaned up and validate that the right findings are being handled.\n\n## Use cases with ready-to-use configurations\n\nEach example below includes a policy configuration you can copy, customize, and apply immediately.\n\n### 1. Dismiss test code vulnerabilities\n\nSAST and dependency scanners flag hardcoded credentials, insecure fixtures, and dev-only dependencies in test directories. These are not production risks.\n\n```yaml\nvulnerability_management_policy:\n  - name: \"Dismiss test code vulnerabilities\"\n    description: \"Auto-dismiss findings in test directories\"\n    enabled: true\n    rules:\n      - type: detected\n        criteria:\n          - type: file_path\n            value: \"test/**/*\"\n      - type: detected\n        criteria:\n          - type: file_path\n            value: \"tests/**/*\"\n      - type: detected\n        criteria:\n          - type: file_path\n            value: \"spec/**/*\"\n      - type: detected\n        criteria:\n          - type: directory\n            value: \"__tests__/*\"\n    actions:\n      - type: auto_dismiss\n        dismissal_reason: used_in_tests\n\n```\n\n### 2. Dismiss vendored and third-party code\n\nVulnerabilities in `vendor/`, `third_party/`, or checked-in `node_modules` are managed upstream and not actionable for your team.\n\n```yaml\nvulnerability_management_policy:\n  - name: \"Dismiss vendored dependency findings\"\n    description: \"Findings in vendored code are managed upstream\"\n    enabled: true\n    rules:\n      - type: detected\n        criteria:\n          - type: directory\n            value: \"vendor/*\"\n      - type: detected\n        criteria:\n          - type: directory\n            value: \"third_party/*\"\n      - type: detected\n        criteria:\n          - type: directory\n            value: \"vendored/*\"\n    actions:\n      - type: auto_dismiss\n        dismissal_reason: not_applicable\n\n```\n\n### 3. Dismiss known false positive CVEs\n\nCertain CVEs are repeatedly flagged but don't apply to your usage context. Teams dismiss these manually every time they appear. Replace the example CVEs below with your own.\n\n```yaml\nvulnerability_management_policy:\n  - name: \"Dismiss known false positive CVEs\"\n    description: \"CVEs confirmed as false positives for our environment\"\n    enabled: true\n    rules:\n      - type: detected\n        criteria:\n          - type: identifier\n            value: \"CVE-2023-44487\"\n      - type: detected\n        criteria:\n          - type: identifier\n            value: \"CVE-2024-29041\"\n      - type: detected\n        criteria:\n          - type: identifier\n            value: \"CVE-2023-26136\"\n    actions:\n      - type: auto_dismiss\n        dismissal_reason: false_positive\n\n```\n\n### 4. Dismiss generated and auto-created code\n\nProtobuf, gRPC, OpenAPI generators, and ORM scaffolding tools produce files with flagged patterns that cannot be patched by your team.\n\n```yaml\nvulnerability_management_policy:\n  - name: \"Dismiss generated code findings\"\n    description: \"Generated files are not authored by us\"\n    enabled: true\n    rules:\n      - type: detected\n        criteria:\n          - type: directory\n            value: \"generated/*\"\n      - type: detected\n        criteria:\n          - type: file_path\n            value: \"**/*.pb.go\"\n      - type: detected\n        criteria:\n          - type: file_path\n            value: \"**/*.generated.*\"\n    actions:\n      - type: auto_dismiss\n        dismissal_reason: not_applicable\n\n```\n\n### 5. Dismiss infrastructure-mitigated vulnerabilities\n\nVulnerability classes like XSS (CWE-79) or SQL injection (CWE-89) that are already addressed by WAF rules or runtime protection. Only use this when mitigating controls are verified and consistently enforced.\n\n```yaml\nvulnerability_management_policy:\n  - name: \"Dismiss CWEs mitigated by WAF\"\n    description: \"XSS and SQLi mitigated by WAF rules\"\n    enabled: true\n    rules:\n      - type: detected\n        criteria:\n          - type: identifier\n            value: \"CWE-79\"\n      - type: detected\n        criteria:\n          - type: identifier\n            value: \"CWE-89\"\n    actions:\n      - type: auto_dismiss\n        dismissal_reason: mitigating_control\n\n```\n\n### 6. Dismiss CVE families across your organization\n\nA wave of related CVEs for a widely-used library your team has assessed? Apply at the group level to dismiss them across dozens of projects. The wildcard pattern (e.g., `CVE-2021-44*`) matches all CVEs with that prefix.\n\n```yaml\nvulnerability_management_policy:\n  - name: \"Accept risk for log4j CVE family\"\n    description: \"Log4j CVEs mitigated by version pinning and WAF\"\n    enabled: true\n    rules:\n      - type: detected\n        criteria:\n          - type: identifier\n            value: \"CVE-2021-44*\"\n    actions:\n      - type: auto_dismiss\n        dismissal_reason: acceptable_risk\n\n```\n\n## Quick reference\n\n| Parameter | Details |\n|-----------|---------|\n| **Criteria types** | `file_path` (glob patterns, e.g., `test/**/*`), `directory` (e.g., `vendor/*`), `identifier` (CVE/CWE with wildcards, e.g., `CVE-2023-*`) |\n| **Dismissal reasons** | `acceptable_risk`, `false_positive`, `mitigating_control`, `used_in_tests`, `not_applicable` |\n| **Criteria logic** | Multiple criteria within a rule = AND (must match all). Multiple rules within a policy = OR (match any). |\n| **Limits** | 3 criteria per rule, 5 rules per policy, 5 policies per security policy project. Vulnerabilty management policy actions process 1000 vulnerabilities per pipeline run in the target project, until all matching vulnerabilities are processed. |\n| **Affected statuses** | Needs triage, Confirmed |\n| **Scope** | Project-level or group-level (group-level applies across all projects) |\n\n## Getting started\nHere's how to get started with auto-dismiss policies:\n\n1. **Identify the noise.** Open your vulnerability report and sort by \"Needs triage.\" Look for patterns: test files, vendored code, the same CVE across projects.\n\n2. **Pick a scenario.** Start with whichever use case above accounts for the most findings.\n\n3. **Record your baseline.** Note the number of \"Needs triage\" vulnerabilities before creating a policy.\n\n4. **Create and enable.** Navigate to **Secure > Policies > New policy > Vulnerability management policy**. Paste the configuration from the use case above, then merge the MR.\n\n5. **Validate results.** After the next default-branch pipeline, filter by status \"Dismissed\" to confirm the right findings were handled.\n\nFor full configuration details, see the [vulnerability management policy documentation](https://docs.gitlab.com/user/application_security/policies/vulnerability_management_policy/#auto-dismiss-policies).\n\n> Ready to take control of vulnerability noise? [Start a free GitLab Ultimate trial](https://about.gitlab.com/free-trial/) and configure your first auto-dismiss policy today.\n",{"slug":744,"featured":29,"template":15},"auto-dismiss-vulnerability-management-policy",{"content":746,"config":755},{"title":747,"description":748,"authors":749,"heroImage":751,"date":752,"body":753,"category":11,"tags":754},"GitLab 18.10 brings AI-native triage and remediation ","Learn about GitLab Duo Agent Platform capabilities that cut noise, surface real vulnerabilities, and turn findings into proposed fixes.",[750],"Alisa Ho","https://res.cloudinary.com/about-gitlab-com/image/upload/v1773843921/rm35fx4gylrsu9alf2fx.png","2026-03-19","GitLab 18.10 introduces new AI-powered security capabilities focused on improving the quality and speed of vulnerability management. Together, these features can help reduce the time developers spend investigating false positives and bring automated remediation directly into their workflow, so they can fix vulnerabilities without needing to be security experts.\n\nHere is what’s new:\n\n* [**Static Application Security Testing (SAST) false positive detection**](https://docs.gitlab.com/user/application_security/vulnerabilities/false_positive_detection/) **is now generally available.** This flow uses an LLM for agentic reasoning to determine the likelihood that a vulnerability is a false positive or not, so security and development teams can focus on remediating critical vulnerabilities first.  \n* [**Agentic SAST vulnerability resolution**](https://docs.gitlab.com/user/application_security/vulnerabilities/agentic_vulnerability_resolution/) **is now in beta.** Agentic SAST vulnerability resolution automatically creates a merge request with a proposed fix for verified SAST vulnerabilities, which can shorten time to remediation and reduce the need for deep security expertise.  \n* [**Secret false positive detection**](https://docs.gitlab.com/user/application_security/vulnerabilities/secret_false_positive_detection/) **is now in beta.** This flow brings the same AI-powered noise reduction to secret detection, flagging dummy and test secrets to save review effort.\n\nThese flows are available to GitLab Ultimate customers using GitLab Duo Agent Platform. \n\n## Cut triage time with SAST false positive detection\n\nTraditional SAST scanners flag every suspicious code pattern they find, regardless of whether code paths are reachable or frameworks already handle the risk. Without runtime context, they cannot distinguish a real vulnerability from safe code that just looks dangerous.\n\nThis means developers could spend hours investigating findings that turn out to be false positives. Over time, that can erode confidence in the report and slow down the teams responsible for fixing real risks.\n\nAfter each SAST scan, GitLab Duo Agent Platform automatically analyzes new critical and high severity findings and attaches:\n\n* A confidence score indicating how likely the finding is to be a false positive  \n* An AI-generated explanation describing the reasoning  \n* A visual badge that makes “Likely false positive” versus “Likely real” easy to scan in the UI\n\nThese findings appear in the [Vulnerability Report](https://docs.gitlab.com/user/application_security/vulnerability_report/), as shown below. You can filter the report to focus on findings marked as “Not false positive” so teams can spend their time addressing real vulnerabilities instead of sifting through noise.\n\n![Vulnerability report](https://res.cloudinary.com/about-gitlab-com/image/upload/v1773844787/i0eod01p7gawflllkgsr.png)\n\n\nGitLab Duo Agent Platform's assessment is a recommendation. You stay in control of every false positive to determine if it is valid, and you can audit the agent's reasoning at any time to build confidence in the model. \n\n\n## Turn vulnerabilities into automated fixes\n\nKnowing that a vulnerability is real is only half the work.  Remediation still requires understanding the code path, writing a safe patch, and making sure nothing else breaks.\n\nIf the vulnerability is identified as likely not be a false positive by the SAST false positive detection flow, the Agentic SAST vulnerability resolution flow automatically:\n\n1. Reads the vulnerable code and surrounding context from your repository  \n2. Generates high-quality proposed fixes  \n3. Validates fixes through automated testing   \n4. Opens a merge request with a proposed fix that includes:  \n   * Concrete code changes  \n   * A confidence score  \n   * An explanation of what changed and why\n\nIn this demo, you’ll see how GitLab can automatically take a SAST vulnerability all the way from detection to a ready-to-review merge request. Watch how the agent reads the code, generates and validates a fix, and opens an MR with clear, explainable changes so developers can remediate faster without being security experts.\n\n\u003Ciframe src=\"https://player.vimeo.com/video/1174573325?badge=0&autopause=0&player_id=0&app_id=58479\" frameborder=\"0\" allow=\"autoplay; fullscreen; picture-in-picture; clipboard-write; encrypted-media; web-share\" referrerpolicy=\"strict-origin-when-cross-origin\" style=\"position:absolute;top:0;left:0;width:100%;height:100%;\" title=\"GitLab 18.10 AI SAST False Positive Auto Remediation\">\u003C/iframe>\u003Cscript src=\"https://player.vimeo.com/api/player.js\">\u003C/script>\n\nAs with any AI-generated suggestion, you should review the proposed merge request carefully before merging.\n\n## Surface real secrets\n\nSecret detection is only useful if teams trust the results. When reports are full of test credentials, placeholder values, and example tokens, developers may waste time reviewing noise instead of fixing real exposures. That can slow remediation and decrease confidence in the scan.\n\nSecret false positive detection helps teams focus on the secrets that matter so they can reduce risk faster. When it runs on the default branch, it will automatically:\n\n1. Analyze each finding to spot likely test credentials, example values, and dummy secrets  \n2. Assign a confidence score for whether the finding is a real risk or a likely false positive  \n3. Generate an explanation for why the secret is being treated as real or noise  \n4. Add a badge in the Vulnerability Report so developers can see the status at a glance\n\nDevelopers can also trigger this analysis manually from the Vulnerability Report by selecting **“Check for false positive”** on any secret detection finding, helping them clear out findings that do not pose risk and focus on real secrets sooner.\n\n## Try AI-powered security today\n\nGitLab 18.10 introduces capabilities that cover the full vulnerability workflow, from cutting false positive noise in SAST and secret detection to automatically generating merge requests with proposed fixes.\n\nTo see how AI-powered security can help cut review time and turn findings into ready-to-merge fixes, [start a free trial of GitLab Duo Agent Platform today](https://about.gitlab.com/gitlab-duo-agent-platform/?utm_medium=blog&utm_source=blog&utm_campaign=eg_global_x_x_security_en_).",[741,11,740],{"featured":14,"template":15,"slug":756},"gitlab-18-10-brings-ai-native-triage-and-remediation",{"promotions":758},[759,773,784,795],{"id":760,"categories":761,"header":763,"text":764,"button":765,"image":770},"ai-modernization",[762],"ai-ml","Is AI achieving its promise at scale?","Quiz will take 5 minutes or less",{"text":766,"config":767},"Get your AI maturity score",{"href":768,"dataGaName":769,"dataGaLocation":246},"/assessments/ai-modernization-assessment/","modernization assessment",{"config":771},{"src":772},"https://res.cloudinary.com/about-gitlab-com/image/upload/v1772138786/qix0m7kwnd8x2fh1zq49.png",{"id":774,"categories":775,"header":776,"text":764,"button":777,"image":781},"devops-modernization",[741,38],"Are you just managing tools or shipping innovation?",{"text":778,"config":779},"Get your DevOps maturity score",{"href":780,"dataGaName":769,"dataGaLocation":246},"/assessments/devops-modernization-assessment/",{"config":782},{"src":783},"https://res.cloudinary.com/about-gitlab-com/image/upload/v1772138785/eg818fmakweyuznttgid.png",{"id":785,"categories":786,"header":787,"text":764,"button":788,"image":792},"security-modernization",[11],"Are you trading speed for security?",{"text":789,"config":790},"Get your security maturity score",{"href":791,"dataGaName":769,"dataGaLocation":246},"/assessments/security-modernization-assessment/",{"config":793},{"src":794},"https://res.cloudinary.com/about-gitlab-com/image/upload/v1772138786/p4pbqd9nnjejg5ds6mdk.png",{"id":796,"paths":797,"header":800,"text":801,"button":802,"image":807},"github-azure-migration",[798,799],"migration-from-azure-devops-to-gitlab","integrating-azure-devops-scm-and-gitlab","Is your team ready for GitHub's Azure move?","GitHub is already rebuilding around Azure. Find out what it means for you.",{"text":803,"config":804},"See how GitLab compares to GitHub",{"href":805,"dataGaName":806,"dataGaLocation":246},"/compare/gitlab-vs-github/github-azure-migration/","github azure migration",{"config":808},{"src":783},{"header":810,"blurb":811,"button":812,"secondaryButton":817},"Start building faster today","See what your team can do with the intelligent orchestration platform for DevSecOps.\n",{"text":813,"config":814},"Get your free trial",{"href":815,"dataGaName":54,"dataGaLocation":816},"https://gitlab.com/-/trial_registrations/new?glm_content=default-saas-trial&glm_source=about.gitlab.com/","feature",{"text":509,"config":818},{"href":58,"dataGaName":59,"dataGaLocation":816},1777493620375]