Source
Certification page (ISO 27001) — Codacy
Checked for Codacy on 6 Nov 2026
- Page
- https://www.codacy.com/iso-27001
- Checked
- 6 Nov 2026, 04:58 UTC
- How we may use it
- Public page, crawling permitted
Technical details
- type
- page
- http status
- 200
- content hash
- sha256:1b3cca5a77435cf6758b81f672bdfcaac2205dc0404155f828ed5ade7c251e3b
- permission
- robots_ok
- screenshot
- Screenshot on file (internal exhibit, not published)
Cited by
Facts read from this source
-
ISO 27001 control a8 25 secure development lifecycle Report an error
“A.8.25 Secure Development Life Cycle Security integrated across the SDLC, inception to deployment”
-
ISO 27001 control a8 26 application security requirements Report an error
“The requirements you define that are automatically testable become rules and thresholds Codacy enforces. Codacy evidences that they’re applied, not that they were defined.”
-
ISO 27001 control a8 28 secure coding Report an error
“Findings are surfaced on the pull request that introduced them, and a failing gate blocks the merge.”
-
ISO 27001 control a8 29 security testing Report an error
“Static analysis of source code, plus dynamic scanning of running applications and APIs, triggered from your pipeline. Penetration testing is a separate requirement, available through our partner.”
-
ISO 27001 control a8 32 change management Report an error
“Gates block the merge until checks pass and a reviewer approves. The check result and the approval are recorded against the pull request. Configuration changes to Codacy itself are recorded in the audit log.”
-
ISO 27001 control a8 8 technical vulnerabilities Report an error
“Daily rescans of open-source dependencies, severity-ranked findings, configurable remediation deadlines with overdue status, and CSV export for review.”
-
Audit log purpose Report an error
“Changes to your Codacy analysis settings are recorded, so you can show the standard wasn’t quietly loosened.”
-
Sast scope Report an error
“SAST reads your source code for supported vulnerability classes. DAST tests your running applications and APIs, on demand from your pipeline.”
-
Sast rule alignment Report an error
“Configure your secure coding standard once, from OWASP and CWE-aligned rules, and Codacy applies it at every commit across every connected repository.”
-
Sast vulnerability classes Report an error
“Injection patterns, insecure cryptography, and authentication and authorization weaknesses, identified before merge.”
-
Dependency rescan timing Report an error
“Dependencies are reassessed between commits, so a vulnerability disclosed today surfaces today, not at the next code change.”
-
Finding deadline tracking Report an error
“Set a remediation deadline per severity. Each finding shows its age, its status, and whether it has gone overdue.”
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 Source-code handling, security & compliance
- The Engineering Manager Code analysis (SAST & code quality)
- The Engineering Manager Source-code handling, security & compliance
- The Lead Developer Code analysis (SAST & code quality)
- The Lead Developer Source-code handling, security & compliance
- The Platform Engineer Code analysis (SAST & code quality)
- The Platform Engineer Source-code handling, security & compliance
- The Product Security Officer Code analysis (SAST & code quality)
- The Product Security Officer Source-code handling, security & compliance
- The Skeptic Code analysis (SAST & code quality)
- The Skeptic Source-code handling, security & compliance