Handout-CSAM Q1 2025
Handout-CSAM Q1 2025
Topics:
• How to use CSAM to discover and manage assets.
• How to manage security gaps.
• How to use CSAM to implement data hygiene.
• How to report and respond to inventory risks.
01 Why CSAM?
Example answers:
• My asset inventory is too hard to keep up to date
• My asset inventory isn’t detailed enough
• I don’t know all of my internet-facing assets
• I am able to view asset inventory using a siloed tool, however unable to
map asset risk factors to VMDR module
• I am unable to track and manage stale assets
• My Organization is using ServiceNow CMDB for asset management, how
do I sync this information with Qualys?
• Unified cyber asset inventory enables IT & Security teams to correlate sources of asset inventory.
• Business context from 3rd party is indexed for search, reports, dashboards, and for dynamic tagging.
• Import inventory data of third-party services within Qualys CSAM using connectors.
✓ ✓
Get complete visibility into your environment
Discover and inventory all your assets
View categorized and normalized hardware and software information
Standardize your inventory ✓ ✓
✓ ✓
Define criticality and find related assets
Add business context through dynamic tagging (Custom attributes only
available with CSAM)
✓
Setup automated purging for stale assets
Maintain asset hygiene 𝗫
✓
Find and upgrade unsupported software and hardware
Know product lifecycle and support information 𝗫
✓
Eliminate unauthorized software and identify missing security agents from
your environment 𝗫
Quickly identify risk factors
✓
Be informed about assets requiring attention
Receive notifications to review and define actions 𝗫
✓
Inform stakeholders about health of your assets
Create custom reports 𝗫
✓
Easily keep your CMDB and Qualys data up to date
Enable integration to sync with CMDBs such as ServiceNow and Webhook 𝗫
20 Qualys Inc. Corporate Presentation
Discover and Inventory Assets
ry
• Configure CMDB Sync (if using CMDB
solution)
espond
Normalization, Categorization &
r
onito
Enrichment (performed automatically
R
in the Qualys Cloud Platform)
dM
an
3 2
an
or
Organize and Manage Assets Rep
ct
ete
• Configure Asset Tags and custom D
attributes
Qualys sensors collect data from your IT environment and automatically beam it up
to the Qualys Cloud Platform, which continuously analyzes and correlates the
information to help you quickly and precisely identify and eliminate threats.
A Qualys Scanner Appliance has a remote perspective of any host you target. Its ability to perform a
vulnerability assessment test, is directly impacted by the number and type of open service ports on any
given host, as well as the presence of any network filtering devices that might potentially obstruct
individual scan packets.
Passive sensing
Data will be sniffed passively in the subnet by listening to
broadcasts and multicasts Identify Rogue Devices even in IOT environment without a
• Collect rich asset metadata using ARP, massive investment in sensors and new systems
DHCP, SSDP, NetBios, mDNS, CDP/LLDP, LLMNR, WSD and
more.
This means there isn’t enough discovered data for Qualys to determine the
hardware/OS/software.
• Example: If you ran an unauthenticated scan, but we could not fully fingerprint the OS
• Example: Firewall that prohibits certain scan traffic from fully enumerating host
Hardware.category1:`Unknown`
• There likely is enough data for Qualys to categorize the host, but it’s not catalogued yet.
• It is currently being processed against rules and Qualys lab for analysis for categorization.
• This processing happens daily across all asset data.
8→1 20 → 1
Manufacturer Product
OPERATING SYSTEM
Microsoft Windows Server 2022
Raw Data
Raw Data Datacenter (21H2 Insider Preview
Build 20348.169 64-Bit)
Category Windows / Server
OS Publisher Microsoft
Name Windows Server 2022
Market Version 2022
Normalization and Categorization
Edition Datacenter
Microsoft Windows Server 2022
Release Datacenter (21H2 Insider Preview
Build 20348.169)
Architecture 64-Bit
Lifecycle Stage GA
End of Service Oct 14 2031 Advanced Asset Information
License Type Commercial
HARDWARE
Raw Data
IBM Power System S924 9009-
Raw Data
42G
Manufacturer IBM
Model S924
SOFTWARE
Raw Data openssl-1.1.1c-2.el8.x86_64 Raw Data
Publisher OpenSSL
Architecture 64-bit
Use hardware, software, and OS tokens to help “normalize” your query conditions to uncover more
precise asset details.
Examples:
hardware.category1: `Networking Device`
hardware.category2: `Switch`
hardware.category: `Networking Device / Switch`
operatingSystem.category1: `Windows`
operatingSystem.category2: `Server`
operatingSystem.category: `Windows / Server`
software:(category1: `Security`)
software:(category2: `Endpoint Protection`)
software:(category: `Security / Endpoint Protection`)
software:(license.category:`Commercial`)
software:(license.category:`Open Source`)
Operating System
Location
Static Tags:
Assigned manually to host assets
Commonly used as the starting point of an Asset
Tag Hierarchy
Dynamic Tags:
Host assignment is determined by Asset Tag Rule
Engine
Tags dynamically change with updates to host
• Business Units
• Asset Groups
• Asset Search
• Cloud Agent
• Internet Facing Assets
• Passive Sensor
• EASM
A dynamic tag based on an IP subnet. This tag could then be used as the target for vulnerability scans.
Dynamic tags based on likely patch targets. These might be combined in a patch deployment job, such
as deploying patches to Windows servers in the production DNS domain.
Dynamic tags based on asset hardware. You could use this to identify all laptops in the organization and
confirm that each laptop has appropriate client software installed (including the Qualys Cloud Agent).
The logic of this type of tag might be to report on or patch on critical-risk assets:
The assets identified with this tag might then be targeted by the infrastructure team to update or
remove the unwanted software. Qualys Patch Management and Qualys Custom Assessment and
Remediation (”CAR”) can be used for such a purpose.
The logic of this type of tag might be to report to the business the risk level of a particular business
process. This is to help the business owner to understand “Is our Customer Payments System at risk
today?”
This might be identified by installed software, IP range, asset name contains, business information (from
a CMDB), cloud provider tag, or custom attribute.
The following is an example of a static tags. It can be used to exclude assets from a scan or patch job.
Further information about creating Asset Tags can be found in this blog article:
Purging: Irreversible
• Reduce false positives to isolate risk on the external attack surface using EASM lightweight scan
• EASM uses the same tools an attacker would use for doing recon against your organization
• Asset metadata synchronization is performed only for assets already in both Qualys and ServiceNow
• Optionally, asset information is staged for user approval before being written to CMDB
• Preconfigured reports
3. Create schedules, define what data is to be synced and configure mapping for Business Criticality
to Qualys Asset Criticality Score
• Public APIs are for use with other CMDBs (not ServiceNow)
• Qualys Cloud Suite API provides many ways to integrate your programs and API calls with Qualys
capabilities
• CSAM now supports the import of Asset business metadata and Business app metadata from your
CMDB into your Qualys asset inventory using v2 APIs
• Currently supports a maximum of 250 records for import in one API call for both Asset and Business
app metadata
• The user must have access to the CSAM module with API enabled for that role
• Imported business attributes are listed on the Asset Details page
1. Feature Activation
2. Asset Identification Rules Creation
3. Connectors Creation
4. Asset Identification Rule Selection for Connector (Optional)
5. Asset Identification
6. Asset Import in CSAM Inventory
7. Reconciliation Rules Configuration
8. Purge Rule Creation
3. Create connectors for third-party services, discover resources, and pass the information to the
required Qualys modules, such as CSAM.
4. Specify the Asset Identification rules to determine which attributes must be fetched and in which
order. (Optional)
6. After the assets are discovered based on the asset identification rules selected for the respective
connector, they are merged and imported into the CSAM inventory.
Reconciliation Rules: are essential when you want to merge assets that come from Qualys native
sensors like Qualys agent or scanner when there are assets already identified by the third-party sources
before they are discovered again through a different schedule.
You can create purge rules to purge, i.e. remove data, for some third-party assets discovered by various
connectors.
Note: Purging can be done for assets being discovered/scanned by various sensors.
ry
Product Lifecycle Management
(EOL/EOS/Obsolete hardware and software
automatically identified
Software Authorization (configure rules to identify
espond
authorized/unauthorized software)
n it o r
You can extend TruRisk to include Inventory Risk
Assessment, with CSAM detections of EoL/EoS,
Mo
unauthorized software & ports, and missing
d
required software. Each vector has a Qualys
an
nd
Detection Score (QDS 1 to 100), to measure 3 2
t
or
severity.
ta
Rep
ec
t
De
Qualys TruRisk places detected vulnerabilities within the context of your critical
and non-critical host assets to help you remediate and fix the vulnerabilities that
count
Both QDS and ARS are calculated values, while ACS is assigned to assets via Asset
Tags
Assets are then assigned the highest criticality score (evaluated across all Asset Tags presently assigned
to the asset).
• Qualys Detection Score (QDS) begins with the CVSS base score of detected vulnerabilities (i.e.,
technical vulnerability details)
• It then adds temporal factors such as Threat Intelligence (including exploit code maturity, associated
malware, active threat actors, and vulnerabilities trending on the dark web)
• Mitigating and remediating controls related to the exposure are included in the QDS calculation
• The critical range indicates CVSS score is critical, there is a weaponized exploit available, and there is
evidence of exploitation by threat actors
• EOL/EOS technology
• Unauthorized Ports
• Unauthorized Software
• Missing Software
Asset Risk Score (ARS) combines the Criticality Score of a single host with a weighted average of its
combined vulnerability detections.
While the Qualys Detection Score provides a useful metric for measuring the impact of a single
vulnerability, the Asset Risk Score places the vulnerability in the context of other vulnerabilities
discovered on the same host.
hardware.lifecycle.stage:value
operatingSystem.lifecycle.stage:value
software:(lifecycle.stage:value)
Generally Available (GA) Generally Available (GA) Generally Available (GA) Low - Product updates and security
patches are readily available.
End-of-Sale (EOS) End-of-Life (EOL) End-of-Life (EOL) Elevated - While product
enhancements and updates have
ended, security patches may still be
provided.
Obsolete (OBS) End-of-Service (EOS) End-of-Service (EOS) High – Product features and updates as
well as security patches have ended.
• Rules can include list of authorized and unauthorized software products, including
software that needs review
D
Visualize Data (use dashboards to identify at risk
ry
assets)
espond
requirements)
r
onito
R
Configure Rule-Based Alerts (define criteria for
d
alert notifications)
dM
t an
an
3
or
Rep 2
ct
ete
D
• Rule/QQL-driven alerts
• Out-of-box templates
• Email, Slack, or PagerDuty notifications
Configure a rule specifying events you want to monitor, criteria for triggering the
rule, and actions to be taken on those events.
2 4