Compliance and Vulnerabilities two different animals

vulnerability management & Compliance

We often come across those questions. are compliance programmes and vulnerability management, posture management different?

Yes and no is the answer. With compliance, we try to be guided by a framework to implement security, while vulnerability management is usually one of the process parts of any of the frameworks

So how do you join the two? easy you look for the elements that match compliance and vulnerabilities

Every compliance framework has similar steps

  • Prepare a plan/programme
  • Collect Assets and assign to users
  • Assess Assets with some form of vulnerability scan
  • Structure a set of actions for the compliance process and assign tasks/targets
  • Execute on those targets
  • measure progress towards green

What are the frameworks you might look into?

First article to focus on vulnerability management, posture management and mapping to compliance framework like CISA, NIST Cybersecurity Framework and ISO27001:2017
Framework of reference

ISO 27001

The ISO/IEC 27001:2013 standard focuses on creating an information security management system (ISMS) that protects confidentiality, integrity, and availability of information as part of the risk management process.

Under ISO 27001:2013, a vulnerability is defined as “a weakness of an asset or control that could potentially be exploited by one or more threats.” A threat is defined as any “potential cause of an unwanted incident, which may result in harm to a system or organization.” 

What Controls can we map in vulnerability management?

-Asset Management

  • Management of technology vuln (12.6.1)
  • Risk assessment controls
  • Software security issues (8.1.1)
  • Logging and monitoring (A12.4)
  • Annex A12.5 – Controls for operational software

NIST Cybersecurity Framework

The NIST Cybersecurity Framework is voluntary guidance based on existing standards, guidelines, and practices for organizations to better manage and reduce cybersecurity risk. In addition to helping organizations manage and reduce risks, it was designed to foster risk and cybersecurity management communications amongst internal and external organizational stakeholders.

https://www.nist.gov/cyberframework/framework

The framework is composed of several parts for brevity, we refer to the core elements that form the framework, for this writeup we will focus only on the main categories and subcategories, citing the individual numbers.

Identify

  • ID-RA-1 – Assets are identified
  • ID-RA 2 – Threat and vulnerabilities are identified

Protect

  • PR.IP-12 – Vuln management plan is developed and implemented
  • PR.IP-7 – Protection Processes are continuously implemented

Detect

  • DE.CM – asset are monitored at intervals
  • DE.DP-5
  • Det. Proc. Are improved
  • DE.CM-8 – Vuln Scans are performed

Respond

  • RS-MI-3 – New Vuln are mitigated, and risk accepted
  • RS-IM – Org resp activities are improved  with lessons learned

Also, another element to look for vulnerability management: https://csrc.nist.gov/publications/detail/sp/800-40/rev-3/final

CISA Vulnerability management

CISA for Vulnerability management is part 4 of the control guidance distributed by CISA and part of the CRR Resource Guide series. This document is one of 10 resource guides developed by the Department of Homeland Security’s (DHS) Cyber Security Evaluation Program (CSEP) to help organizations implement practices identified as considerations for improvement during a Cyber Resilience Review (CRR).1 The CRR is an interview-based assessment that captures an understanding and qualitative measurement of an organization’s operational resilience, specific to IT operations

  • Section 3/4 – Preparation of analysis and resolutions
  • Section 3,4,5 – Process for identification & Analysis are updated and info are kept current
  • Section 5 – Exposure to identified vuln are managed
  • Section 5 – Root Cause of vulnerabilities are addressed

What BOD Regulation Vulnerability management help

  • BOD 22-01 – Reducing the Significant Risk of Known Exploited Vulnerabilities 
  • BOD 20-01 – Develop and Publish a Vulnerability Disclosure Policy
  • BOD 19-02 – Vulnerability Remediation Requirements for Internet-Accessible Systems
  • BOD 18-02 – Securing High Value Assets

Where you can find the complete list: https://www.cisa.gov/sites/default/files/publications/CRR_Resource_Guide-VM_0.pdf

Following a mapping link to NIST, CISA and the various controls/sections

CRR Goal and Practice [CERT-RMM Reference]NIST CSF Category/ SubcategoryVulnerability Management Resource Guide Reference
Goal 1 – Preparation for vulnerability analysis and resolution activities is conducted.
1. Has a vulnerability analysis and resolution strategy been developed? [VAR: SG1.SP2]PR.IP-12: A vulnerability management plan is developed and implemented
Section III, Step 3 
Section IV, Step 1 
2. Is there a standard set of tools and/or methods in use to identify vulnerabilities in assets? [VAR: SG1.SP2]DE.CM: The information system and assets are monitored at discrete intervals to identify cybersecurity events and verify the effectiveness of protective measures.Section III, Step 2 
Section IV, Step 1 
Goal 2 – A process for identifying and analyzing vulnerabilities is established and maintained.
1. Have sources of vulnerability information been identified? [VAR: SG2.SP1]ID.RA-2: Threat and vulnerability information is received from information sharing forums and sources
Section III, Step 2 
Section IV, Step 1 
Section IV, Step 5 
2. Is the information from these sources kept current? [VAR: SG2.SP1]DE.DP-5: Detection processes are continuously improved
ID.RA-2: Threat and vulnerability information is received from information sharing forums and sources
PR.IP-7: Protection processes are continuously improved
Section IV, Step 8 
3. Are vulnerabilities being actively discovered? [VAR: SG2.SP2]DE.CM-8: Vulnerability scans are performed
ID.RA-1: Asset vulnerabilities are identified and documented
 –
4. Are vulnerabilities categorized and prioritized? [VAR: SG2.SP3]PR.IP-12: A vulnerability management plan is developed and implementedSection V, Step 4
5. Are vulnerabilities analyzed to determine relevance to the organization? [VAR: SG2.SP3]PR.IP-12: A vulnerability management plan is developed and implementedSection V, Step 4
Section V, Step 5
Section V, Step 7
6. Is a repository used for recording information about vulnerabilities and their resolution? [VAR: SG2.SP2]ID.RA-1: Asset vulnerabilities are identified and documented
PR.IP-12: A vulnerability management plan is developed and implemented
Section IV, Step 1 
Section IV, Step 6 
Section V, Step 5 
Section V, Step 6 
Section V, Step 7 
Mapping Table

How we can help

Phoenix Security helps identify elements related to regulation and help automate and scale most of the regulation above.

Francesco is an internationally renowned public speaker, with multiple interviews in high-profile publications (eg. Forbes), and an author of numerous books and articles, who utilises his platform to evangelize the importance of Cloud security and cutting-edge technologies on a global scale.

Discuss this blog with our community on Slack

Join our AppSec Phoenix community on Slack to discuss this blog and other news with our professional security team

From our Blog

Learn how to predict ransomware risks and vulnerability exploitation using a threat-centric approach. Explore data-driven insights, verified exploit trends, and methods for assessing the likelihood of attacks with key references to CISA KEV, EPSS, and Phoenix Security’s 4D Risk Formula.
Francesco Cipollone
Remote Code Execution flaws continue to undermine Kubernetes ingress integrity. IngressNightmare (CVE-2025-1097, CVE-2025-1098, CVE-2025-24514, CVE-2025-1974) showcases severe threat vectors in NGINX-based proxies, leading to cluster-wide exposure. ASPM, robust remediation tactics, and strong application security solutions—like Phoenix Security—mitigate these vulnerabilities before ransomware groups exploit them.
Francesco Cipollone
Remote Code Execution flaws continue to undermine Kubernetes ingress integrity. IngressNightmare (CVE-2025-1097, CVE-2025-1098, CVE-2025-24514, CVE-2025-1974) showcases severe threat vectors in NGINX-based proxies, leading to cluster-wide exposure. ASPM, robust remediation tactics, and strong application security solutions—like Phoenix Security—mitigate these vulnerabilities before ransomware groups exploit them.
Francesco Cipollone
The recent Google acquisition of Wiz for $32 billion has sent shockwaves through the cybersecurity industry, particularly in the realm of Application Security Posture Management (ASPM). This monumental deal highlights the critical importance of cloud security and the growing demand for robust ASPM solutions. While the acquisition promises potential benefits for Google Cloud users, it also raises concerns about vendor lock-in and the future of cloud-agnostic security. Explore the implications of this acquisition and discover how neutral ASPM solutions like Phoenix Security can bridge the gap in multi-cloud environments, ensuring continuous, collaborative, and comprehensive security from code to cloud.” – Find Assets/Vulns by Scanner – Detailed findings Location information Risk-based Posture Management – Risk and Risk Magnitude for Assets – Filter assets and vulnerabilities by source scanner Integrations – BurpSuite XML Import – Assessment Import API Other Improvements – Improved multi-selection in filters – New CVSS Score column in Vulnerabilities
Alfonso Eusebio
The team at Phoenix Security pleased to bring you another set of new application security (ASPM) features and improvements for vulnerability management across application and cloud security engines. This release builds on top of previous releases with key additions and progress across multiple areas of the platform. Application Security Posture Management (ASPM) Enhancements • New Weighted Asset Risk Formula – Refined risk aggregation for tailored vulnerability management. • Auto-Approval of Risk Exceptions – Accelerate mitigation by automating security approvals. • Enhanced Risk Explorer & Business Unit Insights – Monitor and analyze risk exposure by business units for better prioritization. Vulnerability & Asset Management • Link Findings to Existing Tickets – Seamless GitHub, ServiceNow, and Azure DevOps integration. • Multi-Finding Ticketing for ADO – Group multiple vulnerabilities in a single ticket for better workflow management. • Filter by Business Unit, CWE, Ownership, and Deployment Environment – Target vulnerabilities with precision using advanced filtering. Cyber Threat Intelligence & Security Enhancements • Cyber Threat Intelligence Premium – Access 128,000+ exploits for better exploitability and fixability metrics. • SBOM, Container SBOM & Open Source Artifact Analysis – Conduct deep security analysis with reachability insights. • Enhanced Lacework Container Management – Fetch and analyze running container details for better security reporting. • REST API Enhancements – Use asset tags for automated deployments and streamline security processes. Other Key Updates • CVE & CWE Columns Added – Compare vulnerabilities more effectively. • Custom Status Management for Findings – Personalize security workflows with custom status configurations. • Impact & Risk Explorer Side Panel – Gain heatmap-based insights into vulnerability distribution and team risk impact. 🚀 Stay ahead of vulnerabilities, optimize risk assessment, and enhance security efficiency with Phoenix Security’s latest features! 🚀
Alfonso Eusebio
Discover CVE-2025-30066 tj-actions/changed-files GitHub Action has been compromised, exposing secrets in CI/CD pipelines and posing a major software supply chain security risk. Attackers injected malicious code into all versions (V1–V45), repointing existing tags to a compromised commit that exfiltrated credentials via GitHub Actions logs. Immediate remediation is required—organizations must scan their repositories, rotate secrets, and replace the action to mitigate risk. Learn how Phoenix Security’s ASPM can automate threat detection and enhance GitHub Actions security.
Francesco Cipollone
Derek

Derek Fisher

Head of product security at a global fintech

Derek Fisher – Head of product security at a global fintech. Speaker, instructor, and author in application security.

Derek is an award winning author of a children’s book series in cybersecurity as well as the author of “The Application Security Handbook.” He is a university instructor at Temple University where he teaches software development security to undergraduate and graduate students. He is a speaker on topics in the cybersecurity space and has led teams, large and small, at organizations in the healthcare and financial industries. He has built and matured information security teams as well as implemented organizational information security strategies to reduce the organizations risk.

Derek got his start in the hardware engineering space where he learned about designing circuits and building assemblies for commercial and military applications. He later pursued a computer science degree in order to advance a career in software development. This is where Derek was introduced to cybersecurity and soon caught the bug. He found a mentor to help him grow in cybersecurity and then pursued a graduate degree in the subject.

Since then Derek has worked in the product security space as an architect and leader. He has led teams to deliver more secure software in organizations from multiple industries. His focus has been to raise the security awareness of the engineering organization while maintaining a practice of secure code development, delivery, and operations.

In his role, Jeevan handles a range of tasks, from architecting security solutions to collaborating with Engineering Leadership to address security vulnerabilities at scale and embed security into the fabric of the organization.

Jeevan Singh

Jeevan Singh

Founder of Manicode Security

Jeevan Singh is the Director of Security Engineering at Rippling, with a background spanning various Engineering and Security leadership roles over the course of his career. He’s dedicated to the integration of security practices into software development, working to create a security-aware culture within organizations and imparting security best practices to the team.
In his role, Jeevan handles a range of tasks, from architecting security solutions to collaborating with Engineering Leadership to address security vulnerabilities at scale and embed security into the fabric of the organization.

James

James Berthoty

Founder of Latio Tech

James Berthoty has over ten years of experience across product and security domains. He founded Latio Tech to help companies find the right security tools for their needs without vendor bias.

christophe

Christophe Parisel

Senior Cloud Security Architect

Senior Cloud Security Architect

Chris

Chris Romeo

Co-Founder
Security Journey

Chris Romeo is a leading voice and thinker in application security, threat modeling, and security champions and the CEO of Devici and General Partner at Kerr Ventures. Chris hosts the award-winning “Application Security Podcast,” “The Security Table,” and “The Threat Modeling Podcast” and is a highly rated industry speaker and trainer, featured at the RSA Conference, the AppSec Village @ DefCon, OWASP Global AppSec, ISC2 Security Congress, InfoSec World and All Day DevOps. Chris founded Security Journey, a security education company, leading to an exit in 2022. Chris was the Chief Security Advocate at Cisco, spreading security knowledge through education and champion programs. Chris has twenty-six years of security experience, holding positions across the gamut, including application security, security engineering, incident response, and various Executive roles. Chris holds the CISSP and CSSLP certifications.

jim

Jim Manico

Founder of Manicode Security

Jim Manico is the founder of Manicode Security, where he trains software developers on secure coding and security engineering. Jim is also the founder of Brakeman Security, Inc. and an investor/advisor for Signal Sciences. He is the author of Iron-Clad Java: Building Secure Web Applications (McGraw-Hill), a frequent speaker on secure software practices, and a member of the JavaOne Rockstar speaker community. Jim is also a volunteer for and former board member of the OWASP foundation.

Join our Mailing list!

Get all the latest news, exclusive deals, and feature updates.

The IKIGAI concept
x  Powerful Protection for WordPress, from Shield Security
This Site Is Protected By
ShieldPRO