How to start an application security program for application security

CETEM and CEM for vulnerability management

Vulnerabilities and the problem of scale for cloud and application security

Vulnerability management is identifying, evaluating, treating, and reporting on security vulnerabilities in systems and the software that runs on them. 

This process, together with the vulnerability assessment, forms the lifecycle of vulnerability. 

Security vulnerabilities refer to a technological weakness of a system, software, infrastructure, cloud taht a threat actor. could exploit 

Why is vulnerability management becoming so vital today?

Vulnerability management is becoming ever so vital due to the increased complexity of the technology stack and more alerts from various vulnerability assessment tools.

The usual step at the lower maturity level of a vulnerability assessment and analysis is to assess all the vulnerabilities individually. With an average vulnerability assessment report containing 2000 individual vulnerabilities, this effort becomes quickly overwhelming. 

Security professionals triage vulnerabilities daily and face the challenge of too many alerts coming from all parts of the organization and technology stacks.

According to the Verizon Data Breach investigation report, Vulnerabilities mismanagement is one of the four factors that leads to vulnerabilities. 

According to research from the Ponemon Institute, 53% of companies spend more time navigating manual processes than actually responding to vulnerabilities.

Due to recent changes in vulnerability declaration, and related time to fix vulnerabilities under CISA BOD 22-01, time to fix vulnerabilities is becoming shorter and more critical.

With the current trend of 35% more CVE declared yearly and security teams being unable to cope with the stress and quitting, 54% of security professionals are considering a career change, it is ever more important to focus on the vulnerabilities that matter most.

Steps of the vulnerability lifecycle 

According to a recent Gartner research on vulnerability management is now evolving in Continous Threat and Exposure Management (CTEM) and becoming a new de facto standard for the vulnerability lifecycle. 

The steps of the process start with

1 – Scoping, Aggregate and consolidate – 

  • Scope the part of the organization that will be subject to the vulnerability management process, Caveat, a lot of organizations start this process too wide and get frustrated quickly. Start small, iterate, and expand
  • Aggregate & Correlate the vulnerability – this part of the process will be iterative and enable cleaning up, deduplicate and prioritising based on the relationship between assets

 2 – Map to business – Correlate business application and environment (cloud, endpoint, containers …) to different parts of the business. This enables the traceability of who owns what and who is responsible for fixing the vulnerabilities. 

3 – Prioritization – Correlation, Contextualization and risk assessment of the vulnerabilities  evaluating the impact and likelihood of exploitability

4 – Triage and Risk assessment – Assessment of the vulnerabilities in their context to determine which one is a true positive or a false positive. This process also includes risk acceptance/assessment and vulnerability exceptions. At this stage, you can start setting a risk tolerance level, and how risky / non-risky you want to be

5 – ACT –  this stage is the execution phase. Plan with teams on what to fix and when, and identify the vulnerabilities that are more at risk (from the prioritization) 

As the CTEM or CEM process depends much on collaboration, the remediation is a collaborative effort between the team assessing and implementing the vulnerability, the rest of the business

What are the areas in scope for vulnerability management 

During vulnerability assessment, the areas that can benefit from vulnerability management are:

Software supply chain security

  • SAST – Static Code Analysis 
  • DAST – Dynamic code analysis assessing 
  • SCA – vulnerability assessment of libraries
  • CI/CD Security – vulnerability assessment of pipelines used to build software
  • SBOM – list of artefacts in a software (with possible vulnerabilities attached to it)
  • Purchased/Built Software – Software being purchased and used as is (usually subject to patches) 

Environmental Security

  • Cloud Security –  vulnerability assessment of cloud environments ( like AWS, Azure, GCP), their misconfiguration and vulnerabilities
  • Network Security
  • Infrastructure Security / Endpoint Security –  vulnerability assessment of servers and endpoints
Phoenix Security Vulnerability Managment Evolution Model

Vulnerability Maturity Model Levels

The levels of maturity measure from very immature (L0) to highly mature (L5). The methodologies considered vary from an absent process (L0) to a more data-driven measured, and controlled process (L5). 

We look at several maturity models from NIST to NCSC guidance and SANS. Despite being good guidance, they are disjointed and look at the problem, not from a risk perspective.

In an effort to improve vulnerability management maturity calculation and move towards a more risk-based approach, we created a model that encompasses application security, patching, vulnerability management, and cloud security. 

Every organisation should go through different maturity levels and SLA/SLO exercises. The following is a good indication of maturity level.


Maturity 0 (mapped to SANS VMM Level 1) – Non Existent
No Asset Register
No Scanning Capabilities
No Vulnerability Management Process
No-Risk assessment of vulnerabilitiesOccasional pentest or manual assessment
No scanning capabilities

Measurement:No measurement or basic pentest results/fixed Maturity 1 (mapped to SANS VMM Level 1) –
Scanning – Some scanning capabilities (early stage)No Asset RegisterOne or two scanners (infrastructure, code) Some Pentesting activity (internal/external)No Vulnerability management processJust Fix vulnerabilities when there is time.Vulnerabilities are fixed when and if discoveredMeasurement:Number of vulnerabilities fixed by severity from the output of each scanner

When organisations are at maturity 1-2, the best and most efficient way is to start with a smaller team, scan and document assets, and demonstrate good control on those projects. 

After this it is easier to replicate the model at scale with a systematic approach while teams get gradually more mature. 


Maturity 2 (mapped to SANS VMM Level 2)Scanning Code, Assessing software with DAST or some dynamic application testing capabilitiesExternal attack surface tested Critical assets pentested regularlyManual triage or some Basic SLA (for a whitepaper on SLA see here) Vulnerabilities fixed when and if discoveredNo asset management or some basic levelSome non formalised vulnerability management processNo risk acceptance or assessment processMeasurement:Number of vulnerabilities fixed by severity from the output of each scanner
Maturity 3 (mapped to SANS VMM Level 3)
Start Using SLA for the whole  (for a whitepaper on SLA see here) Policy & mandate when SLA fix Some basic level of the vulnerability management process, Some basic level of asset managementNo major measurement of vulnerabilities Not a consistent measurement of resolutionMeasurement:Number of vulnerabilities fixed by severity from the output of each scannerSLA Based vulnerability resolution time: Critical, High Medium low resolved at different time

Maturity 4 (mapped to SANS VMM Level 4)Start Using SLA for the whole organisation. Consistent use of Severity Based SLAMove to Exposure Based SLA or Risk based SLAConsistent Pipeline approach for vulnerabilities scanning Scheduled/Regular Pentest, assessmentVulnerabilities fixed when and if discovered
No asset managementMasurements
SLA Based vulnerability resolution time: Critical, High Medium low resolved at different timeRisk based resolution times
Team Security OKr (or beginning of)Risk based vulnerability measurement and resolution 


Maturity 5 (mapped to SANS VMM Level 4)Creating Customised SLA/ SLO for different teams/complexity. Implementing SLA Levels based on Type of asset and risk Consistent use of Severity Based SLAMove to Exposure Based SLA or Risk based SLAEmbedded in Feedback LoopsCreating feedback loops to Customise SLA / SLO for systems in different categories. Confidently breaking pipeline
Using team’s OKR to: Burning down regularly the Backlog of vulnerabilitiesSlack and ticketing system used actively to deliver vulnerabilities resolution to teamsMeasuring team performance & feeding it to higher managementProduct owner report on vulnerability resolution and riskRisk-based approach to vulnerability burndownScheduled/Regular Pentest, assessmentVulnerabilities fixed when and if discoveredAutomatic asset management driven by either the vulnerability scanners, CI/CD, cloud services Measurements:Measured Vulnerability management processStart measuring and feedback the Mean Time To Resolution (MTTR) and Mean Time Open (MTO).  Measuring Vulnerability timelinesTeam Security OKr: Self imposed and agreed objectives with Security teamsRisk based vulnerability measurement and resolution 

For a more comprehensive view of Maturity Models in DevSecOps refer to the modern application security and DevSecOps Book 

For a more comprehensive list of Maturity in vulnerability management, refer to the SANS Maturity Model 


How can Phoenix Security Platform help? 

Phoenix Security risk based vulnerability management for application and cloud security
Phoenix Security risk-based vulnerability management for application and cloud security

Technology is not the holy grail or answer to all the problems. Vulnerability management remains a people & culture, process, and technology problem. 

Phoenix security cloud platform can help automate, correlate and track maturity at scale and facilitate the enforcement of measurements. 

Phoenix offers a way to scale triaging and prioritising vulnerabilities, removing the manual part of security analysis and enabling the security team to scale better, from a 1:10 to 1:40 ratio, react faster (from 290 days average resolution time to 30) and be more efficient in the time spent on each vulnerability. 

With a proven methodology adopted by more than 1000 Security professionals, Phoenix enables security engineers to communicate more effectively with the business in terms of risk and loss as well as automatically prioritise vulnerabilities for developers

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

Phoenix Security now integrates with Google Cloud (GCP) Security Center, enabling comprehensive vulnerability management and ASPM across GCP, AWS, and Azure. Prioritize and manage vulnerabilities with enhanced Lacework integration for container security and cloud misconfigurations.- Associate assets with multiple Applications and Environments – Mapping of vulnerabilities to Installed Software – 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
Phoenix Security proudly announces the launch of advanced features designed to enhance Application Security Posture Management (ASPM), streamline vulnerability management, and improve vulnerability remediation campaigns. Our latest capabilities empower security teams to monitor and remediate vulnerabilities at scale, utilizing an advanced AI system that rapidly categorizes vulnerabilities and suggests optimal campaigns for scheduling. This new AI-driven approach aligns with our One Backlog feature and Security Champion initiative, both focused on remediating systemic vulnerabilities and reducing team burnout. Recognized as a Gartner Top ASPM provider in the Voice of the Customer 2024, Phoenix Security has collaborated with leading clients to develop innovative solutions that address the complexities of vulnerability remediation. Our campaigns facilitate real-time monitoring, improve collaboration across teams, and ensure that organizations can effectively respond to evolving security threats, including high-impact vulnerabilities like Log4j. Explore how Phoenix Security can transform your vulnerability management practices and enhance your organization’s overall security posture. – Mapping of vulnerabilities to Installed Software – 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
Francesco Cipollone
What the heck is ASPM and how modern ASPM address new challenges? In this article we explore Application Security Posture Management (ASPM) and how it has become essential for organizations looking to safeguard their applications throughout the software development lifecycle (SDLC). But what truly defines a modern ASPM solution? In this article, we delve into the typical ASPM vendors, explore edge cases, and outline the fundamental pillars that unite them. At Phoenix Security, we recognize the challenges posed by diverse organizational structures, making ASPM as much about data and culture as it is about vulnerability management. That’s why we’ve introduced our ONE BACKLOG feature, which merges security champion initiatives with vulnerability workflows into a single, actionable dashboard. This integration empowers security teams to maintain a comprehensive view of vulnerabilities across code, cloud, and other artifacts, streamlining prioritization and remediation efforts. ASPM is more than just a framework; it’s a proactive strategy that fosters collaboration between development, security, and operations teams. With benefits like unified visibility, risk-based prioritization, and continuous monitoring, organizations can effectively identify and address vulnerabilities, ensuring a robust security posture. Join us as we explore the future of ASPM, focusing on code-to-cloud native solutions, maximizing existing tools, and nurturing a culture of security that transcends traditional barriers. Learn how ASPM can revolutionize your approach to application security and enhance your organization’s resilience in an ever-evolving threat landscape.
Francesco Cipollone
Enhance your vulnerability management with Application Security Posture Management (ASPM) and reachability analysis. Discover how ASPM helps prioritize exploitable vulnerabilities, reduce security noise, and improve risk management. Learn about advanced techniques like code and container reachability, contextual deduplication, and Phoenix Security’s cutting-edge solutions for smarter, more effective application security.
Francesco Cipollone
Phoenix Security’s Application Security Posture Management (ASPM) introduces Reachability Analysis and Contextual Deduplication to revolutionize vulnerability management. These features help security teams prioritize risks by correlating vulnerabilities from code to runtime, focusing on what’s exploitable. With contextual deduplication, Phoenix reduces vulnerability noise by up to 95%, ensuring only real threats are addressed. Stay ahead with 4D Risk Quantification, combining business criticality, network, and runtime reachability for smarter, more effective security.- Associate assets with multiple Applications and Environments – Mapping of vulnerabilities to Installed Software – 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
Francesco Cipollone
Phoenix Security now integrates with Google Cloud (GCP) Security Center, enabling comprehensive vulnerability management and ASPM across GCP, AWS, and Azure. Prioritize and manage vulnerabilities with enhanced Lacework integration for container security and cloud misconfigurations.- Associate assets with multiple Applications and Environments – Mapping of vulnerabilities to Installed Software – 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
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