Discover vulnerable software, prioritize real risks, and track remediation through one centralized security platform.
Introduction
Keeping computers secure involves more than detecting malware. A computer can be free of known malware and still be exposed to security vulnerabilities in its operating system or installed applications.
An outdated application, an unpatched Windows component, or software affected by a publicly disclosed vulnerability can create an opportunity for attackers to compromise a system.
This is where Vulnerability Management in CTA — Cyber Threat Analyzer comes in.
CTA's Vulnerability Management module helps security teams identify installed software, correlate software versions with known vulnerabilities, prioritize findings according to risk, and maintain a record of remediation and verification activities.
Instead of treating every vulnerability as equally urgent, CTA combines vulnerability information with additional risk signals to help analysts decide which findings deserve attention first.
In this guide, we'll walk through the main workflow and explain how to use the module effectively.
1. Understand the Vulnerability Management workflow
CTA organizes vulnerability management around a continuous process:
Identify → Enrich → Prioritize → Remediate → Verify → Monitor → Report
Each stage serves a specific purpose.
Identify: Collect software inventory from supported Windows endpoints and the CTA server itself.
Enrich: Retrieve vulnerability intelligence from recognized external sources.
Prioritize: Match installed software against known vulnerabilities and calculate a contextual risk score.
Remediate: Record and route an approved remediation request through CTA's existing response and remediation architecture.
Verify: Record verification evidence to determine whether the issue has actually been addressed.
Monitor: Revisit inventory and findings as software changes and vulnerability intelligence is updated.
Report: Use findings, statistics, and trends to understand the organization's vulnerability exposure.
The objective is not simply to produce a long list of CVEs. It is to create a manageable process for deciding what to fix, tracking progress, and checking the outcome.
2. Start by collecting software inventory
Before CTA can identify software-related vulnerabilities, it needs information about the software installed on monitored machines.
The Windows endpoint agent periodically collects software metadata from Windows uninstall registry locations, including per-user uninstall entries, as well as Windows hotfix and KB information.
The default inventory collection interval is six hours.
CTA also supports collecting inventory from the computer running the CTA server. This capability is useful when you want to include the server in vulnerability management without installing a separate agent on that machine.
To initiate a local collection, use the Inventory This Server PC button in the desktop interface, when available to your administrator account.
The server also has an API endpoint for this operation:
POST /api/v1/vulnerability/inventory/collect-local
The local collector uses Windows registry and hotfix information. On an unsupported operating system, CTA reports that local inventory collection is unsupported rather than inventing inventory data.
What should you do first?
Confirm that the CTA server is running.
Ensure the Windows endpoint agents are connected and able to submit their inventory.
Allow time for the initial inventory collection and processing.
Collect the server's own inventory if you want to include that computer.
Review the inventory records before interpreting vulnerability findings.
Important: Software inventory is evidence of what is registered as installed. A registry entry does not, by itself, prove that a particular executable is present or currently running.
3. Enrich inventory with vulnerability intelligence
Software inventory tells you what is installed. Vulnerability intelligence helps determine whether that software may be affected by a known security issue.
CTA integrates three vulnerability intelligence sources:
National Vulnerability Database (NVD)
The NVD provides CVE records and associated vulnerability information, including Common Platform Enumeration (CPE) data and available CVSS severity scores.
CTA uses this information to help correlate software products and versions with known vulnerabilities.
CISA Known Exploited Vulnerabilities (KEV)
The CISA KEV catalog identifies vulnerabilities known to have been exploited in the wild.
A vulnerability listed in KEV deserves particular attention because there is evidence of exploitation, although the catalog entry alone does not prove that your particular computer has been attacked.
FIRST Exploit Prediction Scoring System (EPSS)
EPSS provides an estimate of the probability that a vulnerability will be exploited in the wild.
CTA uses EPSS information as another input to risk prioritization.
How synchronization works
CTA's server-side service synchronizes vulnerability intelligence automatically by default, with a scheduled interval of approximately 24 hours. Initial NVD synchronization proceeds through the feed in batches and stores its progress, allowing subsequent cycles to continue rather than always restarting from the beginning.
The service subsequently uses incremental NVD updates where applicable.
Administrators can also initiate synchronization through the API:
POST /api/v1/vulnerability/intelligence/sync
External intelligence synchronization requires network access to the relevant sources. In restricted or air-gapped environments, administrators can disable scheduled external synchronization, but the availability of new intelligence will then depend on the data already stored and any separately managed update process.
Tip: After the initial inventory and intelligence synchronization, allow CTA to correlate the collected information before concluding that the environment has no known vulnerabilities.
4. Review vulnerability findings
Once inventory and vulnerability intelligence are available, CTA correlates the information to produce vulnerability findings.
The Vulnerability Management page is designed to present information such as:
Risk score and risk level
CVE identifier
Affected host or endpoint
Software name and version
CVSS score
KEV status
Finding lifecycle status
Confidence information
Start by reviewing the highest-risk findings. Then examine the affected software, host, CVE, and supporting evidence before deciding what action to take.
Why software matching matters
CTA uses a conservative software-to-CVE matching process. It compares vendor and product identity against NVD CPE information and checks installed versions against applicable version boundaries.
Uncertain matches are not automatically promoted to confirmed findings.
This approach helps reduce the risk of treating a vaguely similar software name as proof that a vulnerability applies.
Nevertheless, analysts should validate important findings against the software vendor's advisory, the affected version range, and the actual configuration of the asset.
A vulnerability record is a reason to investigate—not a substitute for technical validation.
5. Understand how CTA prioritizes risk
Not all vulnerabilities pose the same level of risk to an organization.
For example, a vulnerability with a high CVSS score on an isolated test machine may require a different response from a vulnerability known to be exploited on a critical, Internet-facing server.
CTA calculates a risk score using multiple signals, including:
CVSS severity
Presence in the CISA KEV catalog
EPSS score
Exploit availability or observed exploitation
Internet exposure
Asset criticality
Ransomware association
Active threat-intelligence signals
CTA also stores reason codes that explain why a finding received its score.
The resulting risk levels are:
CRITICAL
HIGH
MEDIUM
LOW
UNKNOWN
The score and level help analysts establish a remediation queue rather than relying on CVSS alone.
A practical prioritization strategy
When reviewing the findings, consider the following order:
Vulnerabilities known to be exploited, especially when present on critical or externally exposed assets.
High-risk vulnerabilities affecting servers or systems that support essential business operations.
Vulnerabilities with high exploit-prediction scores or known exploit availability.
Other applicable vulnerabilities that should be addressed through the normal patch-management process.
This is a prioritization approach, not an instruction to ignore lower-ranked findings. Risk acceptance and remediation deadlines should follow your organization's security policy.
6. Manage the finding lifecycle
Discovering a vulnerability is only the beginning. Teams need to record what they have learned, what they plan to do, and whether the issue has been resolved.
CTA supports the following finding lifecycle states:
| Status | Purpose |
|---|---|
NEW | A newly recorded finding |
CONFIRMED | A finding reviewed and confirmed by an analyst |
OPEN | A finding requiring action |
IN_PROGRESS | Remediation or other handling is underway |
MITIGATED | A mitigation has been applied |
PATCHED | The finding is recorded as patched |
VERIFIED | Verification has confirmed the reported outcome |
ACCEPTED | The risk has been accepted |
FALSE_POSITIVE | The finding has been determined to be a false positive |
NOT_APPLICABLE | The vulnerability does not apply to the assessed situation |
REOPENED | A previously handled finding requires attention again |
Use these states to keep the vulnerability queue meaningful and to distinguish newly identified issues from those actively being addressed.
For example, if an analyst confirms that a vulnerable application is installed on a production server, the finding can be tracked as confirmed or open while the team schedules an appropriate remediation.
Once work begins, its status can reflect that progress. After the change, verification should be recorded separately.
Do not mark a vulnerability as verified simply because a remediation request was created. Creating a request is not proof that the patch was installed or that the vulnerability is no longer present.
7. Record a remediation request
After reviewing a finding, determine the appropriate remediation with the responsible system owner or administrator.
Depending on the vulnerability and the affected system, possible actions include:
Requesting a software or operating-system patch
Installing an approved patch
Disabling an affected feature
Restricting network access
Applying a firewall rule
Disabling an affected service
Improving network segmentation
Monitoring the issue while a permanent fix is prepared
CTA's Vulnerability Management API accepts specific allowlisted remediation action types. A remediation request is recorded and routed through CTA's existing response/remediation control plane.
For example, the API route for a finding is:
POST /api/v1/vulnerability/findings/{finding_id}/remediation
The implementation creates a remediation action record, associates it with the finding and endpoint, and records the request status.
This distinction is important: the Vulnerability Management module records and routes remediation requests; creating a request does not, by itself, prove that the change has been executed successfully.
Before making a production change, confirm the target endpoint, approval, maintenance window, potential service impact, and available rollback procedure. Apply patches and configuration changes using the authorized operational process for the affected system.
8. Verify the result
After remediation, verify the actual state of the affected system.
Depending on the action, useful evidence may include:
The installed software version
The applicable Windows hotfix or KB information
The state of an affected service or feature
Confirmation that the vulnerable version is no longer present
Evidence that a compensating control is operating as intended
CTA supports recording a verification result against a finding through its verification API:
POST /api/v1/vulnerability/findings/{finding_id}/verify
Verification is stored as a separate record. A successful verification can move the finding to VERIFIED.
If the evidence does not establish that the issue has been resolved, do not treat the finding as fixed. Further remediation, investigation, or another verification attempt may be necessary.
This stage closes the loop between identifying a vulnerability and establishing whether the corrective action achieved its intended result.
9. Handle exceptions responsibly
Not every vulnerability can be fixed immediately. A patch may be unavailable, an application may be business-critical, or a change may need to wait for an approved maintenance window.
CTA supports recording exceptions with information such as:
Exception type
Reason
Responsible owner
Approver, where applicable
Expiration date
Compensating controls
Supported exception types include accepted risk, temporary exception, false positive, and not applicable.
A good exception record explains why normal remediation is not currently proceeding, who is accountable for the decision, and what alternative protections are in place.
For temporary exceptions, include a review or expiration date so that the issue does not disappear indefinitely from the team's attention.
Risk acceptance should be an explicit, documented decision—not a substitute for investigating a serious finding.
10. Monitor vulnerability trends
Vulnerability management is an ongoing activity. New software is installed, existing applications are updated, new CVEs are published, and the threat landscape changes.
CTA supports statistics and trend information through its Vulnerability Management API, including:
GET /api/v1/vulnerability/stats
GET /api/v1/vulnerability/trends
These views can help teams understand the state of their vulnerability workload and how it changes over time.
Useful questions to ask during a regular review include:
Are critical and high-risk findings being addressed?
Which endpoints repeatedly appear in the findings?
Are remediation actions progressing within their assigned deadlines?
Are temporary exceptions approaching expiration?
Have previously handled findings reappeared?
Is inventory collection operating as expected?
Has the latest vulnerability intelligence synchronization succeeded?
A declining finding count is useful only when it reflects real improvements. Findings may also disappear because software inventory or intelligence data is incomplete. Review collection and synchronization health alongside the vulnerability statistics.
11. A recommended daily workflow
For an analyst using CTA, the following routine is a practical starting point.
At the beginning of the day
Check the Vulnerability Management service status.
Review the latest inventory collection and intelligence synchronization results.
Review new critical and high-risk findings.
Validate the most important findings against available software and vendor evidence.
During the day
Assign responsibility for remediation.
Record approved remediation requests.
Track findings that are in progress.
Document temporary exceptions where immediate remediation is not possible.
After remediation
Gather evidence from the affected endpoint.
Record the verification result.
Update the finding's lifecycle status as justified by the evidence.
Review statistics and trends to identify recurring problems.
This process gives the team a repeatable way to move from discovery to action and verification.
12. Know the current scope and limitations
CTA's Vulnerability Management implementation provides a foundation for centralized inventory, vulnerability intelligence, correlation, risk scoring, lifecycle tracking, remediation records, and verification records.
However, users should understand several important boundaries:
Software-to-CVE correlation is designed to be conservative; important findings still require validation.
External intelligence synchronization requires network access unless a suitable alternative update process is provided.
Inventory coverage depends on successful collection from supported systems.
A recorded remediation request is not the same as successful patch installation.
A verification record must be supported by appropriate evidence.
Actual Windows collection, production database deployments, large-fleet performance, and real patch-installation workflows require validation in the intended deployment environment.
Use CTA as part of a controlled vulnerability-management process that includes asset ownership, patch management, change approval, verification, and documented risk decisions.
Conclusion
Effective vulnerability management is not just about finding CVEs. It is about understanding which weaknesses matter most, assigning responsibility, making controlled changes, and confirming that those changes worked.
CTA — Cyber Threat Analyzer brings software inventory, vulnerability intelligence, contextual risk scoring, finding lifecycle management, and remediation tracking together in a centralized workflow.
By regularly reviewing findings, prioritizing based on risk, documenting exceptions, and verifying completed remediation, security teams can turn vulnerability information into a more consistent and accountable security process.
Identify the weakness. Prioritize the risk. Track the remediation. Verify the result.
That is the foundation of effective vulnerability management with CTA.
CTA — Cyber Threat Analyzer: Hunt. Detect. Investigate. Respond.
No comments:
Post a Comment