VULNERABILITY MANAGEMENT

Finding vulnerabilities is the easy part. Knowing which ones to fix first is what management is about.

Corporate infrastructure changes continuously. New assets, applications, versions, services and vulnerabilities emerge while the environment needs to remain operational.

In this context, producing a list of vulnerabilities is not enough.

ADD Solution designs vulnerability management programs to identify exposures, put risk in context, set remediation priorities and continuously validate whether the actions taken have actually reduced the attack surface.

APPLIED ENGINEERING

Priority comes from the combination of severity, exposure and impact.

ADD Solution organizes discovery, context, prioritization, remediation and revalidation to turn technical findings into measurable risk reduction.

Specialists prioritizing vulnerabilities by exposure and operational impact

Architecture, implementation and operations treated as parts of the same responsibility.

A VULNERABILITY IS MORE THAN JUST A CVE

The identifier describes the vulnerability. The environment determines its context.

CVE, severity, asset, exposure, criticality, exploitability and existing controls need to be considered together.

01

Severity

Technical characteristics and potential impact.

02

Exposure

Internal and external reach, and existing controls.

03

Asset

Role, owner and criticality.

04

Exploitability

Evidence and conditions for exploitation.

05

Business

Affected process and dependencies.

Two companies may have the same vulnerability and completely different remediation priorities.
ASSET DISCOVERY

We cannot assess what we do not know exists.

Servers, workstations, network devices, firewalls, appliances, applications, cloud assets, services and unknown assets make up the attack surface within the defined scope.

Vulnerability management begins before the scanner. It begins with understanding the technology landscape.
AI & Observability
INVENTORY & CONTEXT

An IP address alone provides little context.

Hostname, type, system, owner, logical location, service, environment, criticality, exposure and business role help determine priority.

Prioritizing vulnerabilities also requires understanding the assets where they exist.
VULNERABILITY ASSESSMENT

The purpose of scanning is not to produce as many findings as possible.

Network scanning, authenticated scanning, agents, cloud integrations and platform assessments can produce evidence depending on the solution and environment.

The goal is to obtain sufficiently reliable evidence to guide a decision.
AUTHENTICATED SCAN

Observing an asset from the outside and assessing it from within can provide different levels of visibility.

Packages, patches, configurations, software and versions may become visible where supported. Credentials used must be protected; authentication does not eliminate false positives.

PAM & Identity Security
CVE & CVSS

Technical severity matters. Business priority requires more context.

CVE identifies a publicly known vulnerability. CVSS represents its characteristics and severity, but does not determine operational priority on its own.

CVSS + EXPLOITABILITY + EXPOSURE + ASSET CRITICALITY + BUSINESS CONTEXT → PRIORITY
A score helps assess severity. Context helps determine priority.
EXPLOITABILITY

Not every vulnerability is equally likely to be exploited.

Exploit availability, evidence of exploitation, threat intelligence, exposure, preconditions and complexity can enrich the analysis depending on the sources, without predicting attacks precisely.

EXPOSURE

An Internet-accessible vulnerability has a different context from the same vulnerability isolated within an internal network.

Internet-facing status, internal networks, segmentation, firewalls, ACLs, VPN, ZTNA, reachability and published services change the analysis — without making internal assets risk-free.

Network security & firewall
ASSET CRITICALITY

The same finding can have different impacts depending on where it occurs.

Critical servers, workstations, production and development environments, infrastructure and business applications have different confidentiality, integrity and availability requirements.

A vulnerability belongs to an asset. The asset belongs to a business process.
RISK-BASED PRIORITIZATION

Fixing everything immediately is not a strategy. Prioritizing correctly is.

SEVERITY × EXPOSURE × EXPLOITABILITY × CRITICALITY × CONTEXT → PRIORITY

The methodology depends on the program, organization and tools; there is no universal formula.

The remediation queue should represent risk, not just a score.
FALSE POSITIVES & VALIDATION

Before mobilizing a team, we need to trust the evidence.

Version, service, configuration, context, evidence and manual verification when needed increase confidence without fully eliminating false positives.

Automation provides scale. Validation adds confidence.
THREAT INTELLIGENCE

Severity describes the vulnerability. Intelligence adds external context.

Exploited vulnerabilities, known activity and campaign context can enrich prioritization based on available sources, without providing absolute predictive certainty.

REMEDIATION

Detecting a vulnerability does not reduce risk until action is taken.

Patching is not the only possible response. Risk treatment must account for technology, operations and the formal risk management process.

01Patch
02Upgrade
03Configuration change
04Hardening
05Remove service
06Segment
07Restrict access
08Compensating control
09Accept risk
PATCH MANAGEMENT

Vulnerability management and patch management are not the same thing.

Vulnerability management identifies and prioritizes risk. Patch management addresses some of the required fixes through updates where applicable.

Not every vulnerability has a patch. Not every patch has the same priority.
HARDENING

Not every exposure is related to outdated software.

Services, protocols, configurations, administrative interfaces, permissions, defaults, ciphers and access controls also need to be assessed.

COMPENSATING CONTROLS

When an immediate fix is not possible, reducing exposure may still be necessary.

Firewalls, WAF, segmentation, ACL, IPS, ZTNA, isolation, deactivation and access restrictions can mitigate risk depending on the scenario.

Mitigating risk does not mean considering the vulnerability fixed.
Application & web security
EXCEPTIONS & RISK ACCEPTANCE

No exception should simply disappear from the management process.

Justification, owner, risk, compensating control, approval, deadline, review and evidence maintain accountability.

Accepted risk remains known risk and must have a review cycle.
REVALIDATION

Closing a ticket does not prove that the vulnerability no longer exists.

FINDING → REMEDIATION → RESCAN → VALIDATION → CLOSED / REOPENED
Remediation ends when the fix is validated, not when the activity is marked complete.
RECURRENCE

When the same problem keeps returning, the cause may lie in the process.

Golden images, templates, automation, configuration, deployment, patching and baselines can reproduce findings.

Remediating a vulnerability resolves one finding. Addressing the cause can prevent hundreds of them.
ENDPOINTS & SERVERS

Software, systems, services and workloads each require their own context.

Workstations, servers, packages, patches, configurations and inventory connect vulnerability management with EDR/XDR and infrastructure.

Endpoint Security (EDR/XDR) Servers & Storage
NETWORK DEVICES

Switches, firewalls, access points and appliances are also part of the attack surface.

Firmware, software, services, management interfaces, protocols and configurations require infrastructure analysis.

Corporate Networks
CLOUD

In the cloud, software vulnerabilities and security configuration issues can coexist.

VMs, images, workloads, packages, services, exposure and cloud context need to be considered without reducing the program to CSPM alone.

Cloud
WEB APPLICATIONS

Infrastructure and applications may require different methodologies.

There is overlap, but an infrastructure scanner does not automatically replace DAST, SAST or penetration testing.

Application & web security
ASSESSMENT ≠ PENTEST

Finding vulnerabilities at scale and simulating attack paths are related but distinct activities.

Vulnerability assessment provides systematic discovery, scale, recurring evaluations and prioritization. Penetration testing provides targeted assessment, controlled validation, analysis of attack chains and impact assessment within the defined scope.

Vulnerability Management seeks continuity. Pentesting provides targeted depth.
REMEDIATION SLA

Priority needs to translate into deadlines and accountability.

Risk, criticality, exposure and organizational policy guide internal deadlines; there is no universal SLA.

CRITICAL → SHORTEST DEADLINE · HIGH → CONTROLLED DEADLINE · MEDIUM → PLANNED CYCLE · LOW → BACKLOG
METRICS & DASHBOARDS

Counting vulnerabilities is easy. Measuring risk reduction is more useful.

Risk distribution, finding age, remediation time, SLA, recurrence, coverage, critical exposure and reopened findings address the needs of technical, management and executive audiences.

Closing a thousand vulnerabilities means little if the ten most important ones remain open.
CONTINUOUS CYCLE

The environment changes every day. An assessment from six months ago describes a different environment.

DISCOVER → ASSESS → PRIORITIZE → REMEDIATE → VALIDATE → MEASURE → REPEAT
Vulnerability Management is not a periodic scan. It is a continuous process.
MATURITY ASSESSMENT

Does your process end with the scanner report, or does it demonstrate risk reduction?

We assess processes, coverage, context, ownership, risk treatment and measurement to establish a path to meaningful improvement.

01Inventory
02Coverage
03Scanning
04Credentials
05Findings
06Prioritization
07Asset context
08SLAs
09Ownership
10Remediation
11Exceptions
12Revalidation
13Metrics
14Integrations
Assess your program’s maturity
ADD SOLUTION METHOD

Findings translated into measurable exposure reduction.

More than 15 years of experience connecting networking, firewalls, servers, endpoints, cloud, applications, PAM, observability and operations.

  1. 01

    Discover

    Assets and the technology attack surface.

  2. 02

    Identify

    Vulnerabilities and evidence.

  3. 03

    Validate

    Confirm the finding and its context.

  4. 04

    Contextualize

    Connect the asset, exposure and business context.

  5. 05

    Prioritize

    Focus effort according to risk.

  6. 06

    Treat

    Remediate, mitigate or formally accept.

  7. 07

    Revalidate

    Verify the outcome.

  8. 08

    Measure

    Track reduction and recurrence.

  9. 09

    Evolve

    Continuously improve the program.

The scanner finds vulnerabilities. Engineering turns findings into priorities and priorities into measurable exposure reduction.
TECHNOLOGIES & PRODUCTS

Process, engineering, prioritization, remediation and validation.

The tool is one component of the program. Vendors are covered on the dedicated technology pages.

Cybersecurity technologies & products
FREQUENTLY ASKED QUESTIONS

Important decisions about vulnerability management

Objective answers to technical and operational questions that commonly arise before a project.

01Does CVSS determine on its own what should be fixed first?

No. Technical severity must be combined with exposure, exploitability, asset criticality and business context.

02Is Vulnerability Management the same as patch management?

No. Vulnerability management identifies and prioritizes risk; patch management carries out some remediations when updates apply.

03Does vulnerability assessment replace pentesting?

No. An assessment provides systematic, recurring discovery; a penetration test performs targeted evaluation and controlled validation within its scope.

04Does closing a ticket mean the vulnerability has been fixed?

Not necessarily. Revalidation or a rescan must confirm that the exposure no longer exists.

05Does mitigation equate to definitive correction?

No. Compensating controls can reduce exposure, but the vulnerability still requires management and review.

TALK TO A SPECIALIST

Let's talk about Vulnerability Management.

Share the context of your environment, the impact you are seeing and the outcome your organization is looking for. ADD Solution will route the conversation to the most suitable specialists.

CONVERSATION CONTEXTVulnerability Management
ABOUT YOUR REQUESTYou are contacting ADD Solution about Vulnerability Management.
SPECIALIST CONTACT

Turn your context into a clear next step.

Tell us what needs to evolve in Vulnerability Management.

01
About youHow can we contact you?
* Required fields
Your data is sent securely and used only to respond to your request. See our Privacy Policy. · Terms of Use.