Source
Source-code handling, security & compliance — found from sitemap — SonarQube
Checked for SonarQube on 6 Nov 2026
- Page
- https://docs.sonarsource.com/cyber-resilience-act
- Checked
- 6 Nov 2026, 05:18 UTC
- How we may use it
- Public page, crawling permitted
Technical details
- type
- page
- http status
- 200
- content hash
- sha256:c49bdc4e4d6bfb578d10b26bde075885691a4e98c0652df9ba835de5f012885d
- permission
- robots_ok
- screenshot
- Screenshot on file (internal exhibit, not published)
Cited by
Facts read from this source
-
Cra mapping Report an error
“Maps the EU Cyber Resilience Act (CRA) requirements to SonarQube capabilities, including quality gates, Advanced Security, SBOM export, and dependency risk review.”
-
Cra evidence workflow Report an error
“This mapping shows how SonarQube capabilities that are already part of a normal development workflow, including code analysis, pull request checks, quality gates, dependency analysis, and issue tracking, can be configured to strengthen CRA-related controls and provide evidence for compliance and cybersecurity processes.”
-
Sarif import Report an error
“Import external findings through SARIF reports (SonarQube Cloud) or SARIF reports (SonarQube Server) where other security tools are part of the workflow.”
-
Sbom export Report an error
“Review dependencies (SonarQube Cloud) or dependencies (SonarQube Server), export SBOMs at release time, and store release SBOMs with the manufacturer's release records.”
-
Dependency risk reports Report an error
“Review and assign dependency risks (SonarQube Cloud) or dependency risks (SonarQube Server), update statuses, add justification where needed, and use dependency risk reports as evidence.”
-
AI codefix Report an error
“Use AI CodeFix or the SonarQube Remediation Agent, where available, to help prepare fixes for eligible issues.”
-
Cra 2a vulnerabilities Report an error
“SonarQube supports this requirement by identifying vulnerabilities and exploitable weaknesses in first-party code and third-party dependencies before release, and by enforcing quality gates on branches and pull requests.”
-
Cra 2b secure defaults Report an error
“SonarQube supports this requirement by detecting insecure configurations or defaults, such as hardcoded secrets, weak cryptographic parameters, or permissive privileges in all kinds of code, application settings, and Infrastructure as Code.”
-
Cra 2d access control Report an error
“SonarQube supports this requirement by analyzing all access control, authentication, and privilege management functionalities in code for security weaknesses, and by blocking related security issues via quality gates.”
-
Cra 2e data transmission Report an error
“SonarQube supports this requirement by detecting cryptography issues, such as missing data encryption, the use of weak ciphers or protocols, or insecure cryptographic parameters.”
-
Cra 2f integrity Report an error
“SonarQube supports this requirement by identifying critical security vulnerabilities, such as command injection, code injection, SQL injection, prompt injection, or arbitrary file writes/reads that could lead to a security breach and put the integrity of applications, data, or deployment environments at risk.”
-
Cra 2h dos Report an error
“SonarQube supports this requirement by checking for over 1,500 different types of reliability issues. These issues can slow down or even crash the application, and can be effectively used in denial-of-service attacks.”
-
Cra 2j attack surface Report an error
“With SAST, taint analysis, IaC scanning, secrets detection, SCA, Advanced SAST, and quality gates in CI and pull requests, teams can make attack-surface review repeatable and traceable across the SDLC.”
-
Cra part2 1 sbom Report an error
“SonarQube supports this requirement by performing software composition analysis, maintaining dependency and risk inventories, and exporting SBOMs in standard formats.”
-
Cra part2 2 remediation Report an error
“With SCA, quality gates, IDE and MCP integration, AI CodeFix, and the SonarQube Remediation Agent where available, teams can fix issues as code is written, helping reduce the time between detection and remediation across the SDLC.”
-
Cra part2 3 continuous analysis Report an error
“SonarQube supports this requirement by analyzing code continuously in CI, on branches, and on pull requests, and by importing external findings where needed.”
-
Cra part2 6 reports Report an error
“SonarQube supports this requirement by providing security reports that summarize all detected vulnerabilities in first-party code and third-party components, including a CRA-specific security report.”
-
Cra article13 risk assessment Report an error
“SonarQube supports the product cybersecurity risk assessment by providing continuously updated evidence on code vulnerabilities, security hotspots, dependency risks, and remediation status.”
-
Cra article13 5 third party Report an error
“SonarQube supports this requirement by identifying third-party software dependencies, highlighting associated vulnerability and license-policy risks, and providing an option to export SBOMs for review.”
-
Cra article13 6 7 dependency fix Report an error
“For dependency vulnerabilities, SonarQube also provides fix guidance such as affected versions, complete or partial fixed versions, and upgrade information.”
-
Cra workflow evidence steps Report an error
“To use SonarQube outputs as part of a CRA evidence process: Analyze all code continuously in CI and on pull requests.”
-
Advanced security scope Report an error
“Use Advanced Security (SonarQube Cloud) or Advanced Security (SonarQube Server) for SCA, Advanced SAST, dependency risks, and SBOM export.”
1 fact read from this page is not shown because it could not be confirmed on the page as captured.
Scores citing this record
- The Application Security Engineer Code analysis (SAST & code quality)
- The Application Security Engineer Developer workflow, quality gates & fixes
- The Application Security Engineer Platforms, deployment & administration
- The Application Security Engineer Source-code handling, security & compliance
- The Engineering Manager Dependencies (SCA), licences & secrets
- The Engineering Manager Developer workflow, quality gates & fixes
- The Engineering Manager Platforms, deployment & administration
- The Engineering Manager Source-code handling, security & compliance
- The Lead Developer Platforms, deployment & administration
- The Lead Developer Source-code handling, security & compliance
- The Platform Engineer Platforms, deployment & administration
- The Platform Engineer Source-code handling, security & compliance
- The Product Security Officer Dependencies (SCA), licences & secrets
- The Product Security Officer Platforms, deployment & administration
- The Product Security Officer Source-code handling, security & compliance
- The Skeptic Code analysis (SAST & code quality)
- The Skeptic Dependencies (SCA), licences & secrets
- The Skeptic Platforms, deployment & administration
- The Skeptic Source-code handling, security & compliance