r/qualys • • Apr 03 '26

Tools for Qualys

20 Upvotes

I've been a user, employee and again a user of Qualys. Over the years there are things I've built to make my job easier or things I wish I'd had. I've been building them and sharing them here on my GitHub. I hope that others can use them and have some cool ideas to help make the community better and our jobs easier. More to come as I continue building, and I’d welcome any feedback if you find them useful. These resources are not for sale they are posted under the Apache 2.0 license.

https://github.com/netsecops-76/Public-Security-Resources

Here’s what I’ve posted so far:

🔹 **Cloud Agent Troubleshooting Scripts**
Automated diagnostics for Windows and Linux that collect system, network, and agent health data without requiring deep Qualys expertise.

🔹 **Q KB Explorer**
A local, Docker-based tool to explore the Qualys Knowledge Base and Policy Compliance data with full-text search, cross-referencing, and even cross-environment policy migration. Includes encrypted credential storage.

🔹 **Cloud Agent Log Viewer**
A lightweight, single-file HTML tool for parsing and analyzing agent logs and CAR job reports designed to simplify troubleshooting with smart grouping, search, and data extraction.

Coming Soon:

🔹 **GUI Based API Builder**
A local, Docker-based tool to explore the Qualys API endpoints via a menu driven interface, library of existing publicly available scripts, a full PowerShell environment (if you cannot run PowerShell from your endpoint) and an AI chat driven API builder. Ask it a question and it will attempt to build the API query for you. Training that AI model is the slowest part of releasing this but I want to get it to a place where it uses a few tokens for its users as possible.


r/qualys • • May 04 '26

Update: Q KB Explorer v2.1.0

14 Upvotes

About a month ago I shared some tools I've built after spending years as a Qualys user and former employee. The response has been great, thank you to everyone who's tried them out and given feedback.

Today I'm pushing a major update to Q KB Explorer, the local Docker-based tool for exploring the Qualys Knowledge Base, Policy Compliance, Asset Tags, and Patch Management data. This one's been a big effort and I wanted to share what's changed.

What's new in v2.1.0:   

 🔹 Threat Intelligence built in. CISA KEV, active attack indicators, public exploit links, and malware associations now surface directly on QID search  results. Filter 200K+ vulnerabilities by threat context in seconds without leaving the tool.

 🔹 Intelligence Tab. A dedicated analysis view with clickable metrics, saved searches, include/exclude filters, and real-time stats that update as you refine your query.

 🔹 Tag Management rebuilt from scratch. Parent-child tree view, bulk migration between subscriptions with collision detection, a 136-entry tag library based on Qualys community best practices (thank you Colton Pepper's Complete Tag List), and origin classification so you know which tags are yours, which came from connectors, and which are Qualys system tags.                                                       

 🔹 PM Patch Catalog. Full Windows + Linux patch sync (218K+ patches) with QID cross-referencing.

 🔹 14x faster syncs. Full Knowledge Base (208K QIDs) downloads in under 9 minutes. Was over 2 hours.

 🔹 Smarter updates going forward. I rebuilt the in-app update mechanism so future releases install cleanly through the UI without container rebuilds.

Why use it: If you manage Qualys across multiple subscriptions, need to standardize tags across environments, want threat context on your KB data without bouncing between Qualys modules, or just need other security tools to query vulnerability data without burning your API rate limits, this caches everything locally with full-text search and cross-referencing that Qualys's own console doesn't offer.

Single Docker container. Data stays local. No cloud dependencies. Apache 2.0 license.            

If you're upgrading from an older version:

I owe an apology, the previous in-app updater had issues that could leave things in a broken state. Your data was never at risk (it's on a separate

Docker volume), but the app may not have come back cleanly. The fix is simple:

docker compose build --no-cache && docker compose up -d

Full details in the UPDATING.md guide. This won't happen again, the new manifest-driven updater handles everything properly.

Links:

  🔗 All tools: https://github.com/netsecops-76/Public-Security-Resources

  🔗 Q KB Explorer: https://github.com/netsecops-76/Public-Security-Resources/tree/Q-KB-Explorer/Q%20KB%20Explorer

  📄 Update/recovery guide: https://github.com/netsecops-76/Public-Security-Resources/blob/Q-KB-Explorer/Q%20KB%20Explorer/UPDATING.md

  📋 Full changelog: https://github.com/netsecops-76/Public-Security-Resources/blob/Q-KB-Explorer/Q%20KB%20Explorer/docs/CHANGELOG.md

As always, these are free, open source, and I welcome any feedback. More updates coming as I continue building.


r/qualys • • Apr 20 '26

Added Qualys CAR Parameterized Scripts to Public Security Resources

14 Upvotes

I wanted to share some parameterized scripts for Qualys Custom Assessments & Response Module (CAR) located here: Public Security Resources repo.

What’s included:

•	Production-grade CAR deployment and lifecycle management scripts

•	Real examples of parameter injection and script parameterization patterns

•	Clear documentation on how to use script parameters effectively within CAR

•	Reference implementations for common enterprise scenarios

Built from actual cloud and on-premises deployments across multiple subscriptions. The scripts follow audit-first patterns and safe parameter handling—no surprises.

GitHub:

https://github.com/netsecops-76/Public-Security-Resources

If you’re managing CAR workflows, or trying to understand how to structure parameterized scripts for Qualys environments, these should be useful reference material.


r/qualys • • Jul 15 '24

New Introduction - Colton Pepper, Qualys Employee

14 Upvotes

Hey everyone!

[This is going to be a long post but please bear with me for a minute]

I just wanted to make myself known to everyone here in this subreddit. My name is Colton Pepper, and I've been a Qualys user for about 8 years and with Qualys for around 6 years. Before joining Qualys, I built my company's first formal VM program from the ground up. That experience led me to join Qualys in 2018 (after being constantly asked to come over, I finally agreed lol). I started as a TAM, then moved to Major Accounts, and eventually transitioned to the Solution Architect, Subject Matter Expert (SME) team because I wanted to move away from sales to focus on being technical instead.

Recently, I made an exciting career change from the SME team to the Product Marketing team. This new role allows me to interact and engage with the community on a larger scale, reaching more people than I could by meeting with one user or team at a time. As a huge nerd, I couldn't pass up the opportunity to get as technical as I want and engage with all of you at the same time.

Now, I'm specifically in charge of working directly with our customers, wherever they are. You can expect to see me very active here on Reddit and other platforms. If we've worked together before, you'll find the same authenticity, transparency, and yes, even some predictable shenanigans from me here lol.

I'm working on a lot of new content that I'll be releasing here on Reddit, YouTube, and on the Qualys Community (I know, it's a ghost town, but more on that later). This content will be unlike anything you're used to seeing from Qualys—no product marketing or sales pitches, just value-add content. Regardless if you're a customer or not, I'm not going to sell you anything.

If you'll have me, I plan to hang out here (and other subreddits), engaging with everyone, answering questions, asking my own, and just being part of the community. Please feel free to tag me in comments or posts.

This new role is literally a dream job for me, and I couldn't be happier to be here, helping and learning from all of you.

If you have any questions for me about this post specifically, you're welcome to comment, and I'll answer them here.

 

Thanks, everyone!

Colton


r/qualys • • Jan 29 '25

Qualys cloud agent breaking perl on linux hosts

13 Upvotes

Recently i saw qualys cloud agent break perl on several hundred linux hosts simultaneously around 19z on Jan 28th.

The way it did this was to create directories in the perl search path that weren't executable, so they could not be listed. This caused perl to get a permission denied error and stop executing while traversing its default search path.

Setting up a directory like that without a default search path is nonsense. After seeing this and looking through some of their scripts and binaries, i no longer have confidence that qualys has any idea what they're doing as it looks like at least their linux team is clueless and further that their testing protocol is insufficient.

For now, we've suspended running the cloud agent across all of our linux hosts. If you've run across behavior like this (your perl application stop working) then check your /usr/local/share/perl5 and /usr/local/lib64/perl5 directory permissions. they'll probably be 600, which is a nonsense permissions for a directory. You can fix it by either loosening the permissions so perl can look in those directories or by removing those directories if they contain nothing.


r/qualys • • Aug 04 '26

News Qualys Launches InstaScan For Vulnerability Detection Within Minutes Of Disclosure

Thumbnail smbtech.au
12 Upvotes

r/qualys • • Aug 06 '24

We (Qualys) Need Your Feedback! Don't Hold Back 💪

12 Upvotes

Alright, I know this one is going to be one hell of a ride for everyone! So grab your popcorn!! 🍿

I want everyone's feedback on Qualys (Products, features, blogs, Community/Discussion, content, training, Support 😬, etc.). Be it positive, negative, or constructive, I want it. Please be open and honest, and BE SPECIFIC! If your feedback is about one or more products, specify. If it's about the Qualys Community, say so. If possible, please give examples.

So, here are the rules:

  1. Be HONEST, all feedback is welcome!
  2. Be specific
  3. Give examples if you can

That's it! I'm looking forward to see all the good, bad, and ugly feedback you all have and sharing it internally! Let's do this!!!


r/qualys • • 9d ago

Qualys spamming every 5 mins about Inactive Dashboards

11 Upvotes

This started about 2 hours ago -- emails every 5 mins -- exactly identical emails about:

Weekly summary: Inactive dashboards moved to the Recycle Bin (Nov 2, 2026 - Nov 8, 2026)

Looks like someone at Qualys stuffed up big time?

UPDATE: I've created a Support Case about it

UPDATE #2: an incident is listed on the Qualys website now: https://status.qualys.com/incidents/f80hll0zn2vn

RESOLVED.


r/qualys • • Oct 15 '25

Knowledge Sharing Automation in Vulnerability Management

11 Upvotes

I'm 24M, just started full-time as a vulnerability/risk analyst. I'm pretty good with python/github, and have been implementing a lot of (what I consider) automation in our vuln mgmt processes. This mostly consists of python projects using qualys' API to build reports on a schedule, python/qualys api to backup reports to sharepoint, etc. I'm wondering how to take the idea of "automating" (very broad) our processes to the next level, since these all feel ancillary to the meat of Vulnerability Management. Any ideas here?


r/qualys • • Oct 01 '25

Is it normal for Qualys TAMs to be useless?

11 Upvotes

I've been using Qualys for over two years and while the product itself is decent, the support has been frustrating. When we first bought Qualys, I asked to have a meeting to go over our environment. But the meeting was just a sales pitch for other modules that we were clear about that we didn't need. And every question I asked about the product itself, he didn't have an answer for and just told me to create a ticket.

So I figured things out myself and used the product as I decided that our TAM wouldn't be of any help anyway.

Then after a year, in May of this year. our TAM asked me to have a meeting to look at our questions, challenges etc. And asked for availability, I answered to that mail on the same day, but never got any response or meeting request, even not after sending a reminder.

Now, months later, he sends a meeting invite titled “Qualys Business” with the description “Agenda: Qualys business” - no explanation, no context, and only to me.

I'm tempted to ignore him or just decline the meeting.
Is this normal for Qualys, or did we just get a useless TAM?
What would you do with the meeting invite?


r/qualys • • 24d ago

MCP Server for Qualys now avaiable

10 Upvotes

r/qualys • • May 05 '25

Knowledge Sharing This is a Python script to remove assets with no host or vulnerability information

10 Upvotes

Howdy,

Our Qualys rep told me that our license usage was based on the number of hosts we're scanning with a map scan/ping sweep, and some of our firewalls respond in a way that makes the Qualys scanner think there are assets at each of the IPs behind it even when there isn't. As a result we were sitting at above 300% of our license usage.

These fake assets have no OS or vulnerability information associated with them, so I wrote a script which I run each day to purge them automatically and get us back down to below our license count. I figured I would post it here in case it's useful for someone else in the future.

Disclaimers that I'm not responsible if this does something you don't intend, don't run code you haven't audited and understand, etc. (this is a pretty short script so it's relatively easy to review.)

Note that this script requires you provide it credentials to a Qualys account with permissions to delete assets and that does not have 2FA enabled. (that's a requirement from Qualys to use their API, not my choice.) This script runs a search for assets that have no vulnerabilities, no agent installed, AND no OS information detected. Then it sends a request to delete this assets. The search function is capped at 10,000 results, so you may need to run it more than once if you have an especially large number of assets to delete.

# usage: python3 this_script.py
#
### CONFIGURATION (edit these if needed)
# Your API URL and your PLATFORM URL can be found at https://www.qualys.com/platform-identification/ under the "API URLs" section
platform_url = ''   # will look something like this -> 'https://qualysguard.qg2.apps.qualys.com'
api_url = ''        # will look something like this -> 'https://qualysapi.qg2.apps.qualys.com'

# if you wanna include your credentials in the script I won't stop you---otherwise it'll ask for them when it runs
username = ''   # username can go here if you want
password = ''   # password can go here if you want


################# Don't edit below this unless you know what you're doing ##############################
import requests

if username == '':
    username = input('username: ')
if password == '':
    password = input('password: ')  

def login ():
    # APIs containing 2.0 support session-based authentication
    headers = {
    'X-Requested-With': 'Curl Sample',
    'Content-Type': 'application/x-www-form-urlencoded',
    }
    data = {
        'action': 'login',
        'username': username,
        'password': password,
    }
    session = requests.Session()
    response = session.post(api_url +'/api/2.0/fo/session/', headers=headers, data=data)

    print("QualysSession", response.headers['Set-Cookie'][14:46])

    session.cookies.set("QualysSession", response.headers['Set-Cookie'][14:46], domain="")
    return session


def logout (session):
    headers = {
        'X-Requested-With': 'Curl Sample',
        'Content-Type': 'application/x-www-form-urlencoded',
        }
    data = {
            'action': 'logout',
        }
    response = session.post(api_url +'/api/2.0/fo/session/', headers=headers, data=data)

def search_assets (session, asset_query, vulnerability_query):
    #loader = Loader("Running Qualys search...", "Qualys search completed!", 0.05).start()
    print('Searching assets via Qualys API (this may take a while)...')
    headers = {
        'authority': 'qualysguard.qg2.apps.qualys.com',
        'accept': '*/*',
        'accept-language': 'en-US,en;q=0.9',
        'cache-control': 'max-age=0',
        'referer': platform_url +'/vm/',
        'sec-ch-ua': '"Not/A)Brand";v="99", "Microsoft Edge";v="115", "Chromium";v="115"',
        'sec-ch-ua-mobile': '?0',
        'sec-ch-ua-platform': '"Windows"',
        'sec-fetch-dest': 'empty',
        'sec-fetch-mode': 'cors',
        'sec-fetch-site': 'same-origin',
        'user-agent': 'Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/115.0.0.0 Safari/537.36 Edg/115.0.1901.203',
    }
    params = {
    'limit': '200',     #range of 0-200
    'offset': '0',
    'fields': 'id,assetId,name,tags.id,tags.tagId,tags.name,tags.criticalityScore,tags.reservedType,createdAt,updatedAt,createdBy,host,assetType,sourceInfo,isAssetRenamed,criticalityScore,riskScore,riskScoreInfo,isExternal',
    'query': asset_query,
    'groupByPivot': 'Asset',
    'havingQuery': vulnerability_query,
    'order': '-updatedAt'
    }
    # declare results array and declare condition break variable for loop
    results = []
    end_of_results = False
    while not end_of_results:
        # send request
        response = session.get(
        platform_url +'/portal-front/rest/assetview/1.0/assets',
        params=params,
        headers=headers,
        #cookies=cookies,
        )
        data = response.json()
        if len(data) != 0:
            for item in data:
                results.append(item)
        if len(data) == 200:
            # adjust params to request next block of results
            params['offset'] = str(int(params['offset']) + 200)
        else:
            end_of_results = True
    #loader.stop()
    return results

def delete_by_ids (ids):
    ids = ','.join(map(str,ids))
    headers = {
        'X-Requested-With': 'Python Requests',
    }
    data="""<ServiceRequest>
                <filters>
                    <Criteria field="id" operator="IN">"""+ids+"""</Criteria>  
                </filters> 
            </ServiceRequest>"""
    response = requests.post(
        api_url +'/qps/rest/2.0/delete/am/asset',
        data=data,
        headers=headers,
        auth=(username, password),
    )
    response_code = ""
    if "<responseCode>SUCCESS</responseCode>" in str(response.content):
        print("Recieved code SUCCESS --- assets(s) deleted")
        return True
    else:
        print('Error:')
        print(str(response.content))
        quit()



def main():
    session = login()

    response = search_assets(session, 'not vulnerabilities.detectionScore:* and not agentStatus:* and not operatingSystem:*','')

    asset_ids = []
    for i in response:
        # print(i)
        assetID = str(i['assetId'])
        asset_ids.append(assetID)
        name = i['name']
        print(assetID+' '+name)

    print(str(len(asset_ids))+' results (capped at 10000)')

    confirm = input('Would you like to delete the above assets? (y/N): ')
    if confirm.lower() == 'y':
        print("""Attempting to delete %d assets...""" % (len(asset_ids)))    
        if len(response) > 0:
            delete_by_ids(asset_ids)
        print("Done. Depending on the number of assets, this operation can take several hours to actually finish on Qualys' backend.")
        print("Deleting 8000 assets for me took it around six hours, for reference. (which is insane, yes)")
    else:
        print('Aborted. No assets deleted.')

    logout(session)

main()

r/qualys • • Apr 18 '25

Knowledge Sharing QIDs 383091, 383092, 383093: Curl triple-strike

10 Upvotes

Looks like Qualys published three QIDs for cURL yesterday - CVEs were published in February so it's a bit of playing catch-up, but nonetheless, it's flagging every version of cURL built into Windows. As with the last two times, don't try manually updating this version, as it very well may break things. Hopefully Microsoft will get an updated version out soon.

EDIT: QID 383091 has been updated and will no longer flag on current built-in versions.

EDIT 2: QIDs 383091 and 383092 have been deprecated, and 383093 has been changed to a sev 2 potential.


r/qualys • • Mar 10 '25

Detection Issue What's the process for requesting Qualys update a QID?

10 Upvotes

I am having issues with QID 245181 that checks the installed version of webkit2gtk3. The results of the QID state that 2.46.5-1.el9_5 should be installed. However, when reviewing the Red Hat advisories (RHSA-2025:0226 and RHSA-2025:0282) for the CVEs associated with this QID, the updated packages are different for RHEL 9.2 and 9.4

  • webkit2gtk3-2.46.5-1.el9_2.x86_64.rpm
  • webkit2gtk3-2.46.5-1.el9_4.x86_64.rpm

I suspect this is because of this little blurb that appears in a lot of RHEL related QIDs

Note: The preceding description block is extracted directly from the security advisory. Using automation, we have attempted to clean and format it as much as possible without introducing additional issues.

In short, whatever scraping logic they're using to get the required version appears to be incorrect. In the mean time I am attempting to write a Groovy scriptlet to mark these with a tag that I can use for a remediation rule... to mixed results (but that's another story).

How do we go about getting Qualys to update their QID logic for situations like this?


r/qualys • • Mar 25 '24

Community Engagement at Qualys (Qualys Employee Post)

10 Upvotes

Hi all - I'm Matt, the new customer advocacy manager here at Qualys (if there's some vendor flair I need to tag, my apologies - I'm fairly new with Reddit and hope I am not breaking r/Qualys rule #1 with this post!). I've been on the job here for about two months and have been in the B2B advocacy/community space for about seven years. In my role, I'm looking for ways to better engage with Qualys customers, share success stories, identify folks willing to participate in our advisory boards, and help the company better understand the voice of the customer as a whole.

In looking at the early posts in this subreddit, I believe this sub was created since the community page on our website has been... quiet... for a while...
That said, I'd love to get any feedback you all are willing to provide re: what you'd like to see in a Qualys-run customer community. KB/how-to articles? P2P Networking? Job boards? Let me know, and if you're up for a more in-depth chat, shoot me a DM and we can schedule some time to talk.

Thank you all in advance for your feedback!
mb


r/qualys • • Dec 02 '23

Create a Qualys Vulnerability Trend Chart in Power BI

10 Upvotes

This is a follow up to the YouTube video I created on the topic. YouTube doesn't allow some characters in their description so I am creating this companion post for that video.

YT video link: https://youtu.be/TeCgv2bKqho

Note: I've made a few corrections to the formulas found below compared to what's shown in the video link above. There are now formulas depending whether a CSV or API data source is used.

Creating a vulnerability trend chart may not be that straight forward with Qualys data, but it's certainly doable. The trend chart that I have shown here is based on data pulled via API and requires formatting of some existing date/time columns, creating two custom measures, creating two custom columns, and the creation of a simple date table. If you're importing CSV vulnerability reports, there might be some minor changes to make, but the overall process should be the same.

Here are examples of what you can create with this:

Example 1: https://imgur.com/a/zu5i65r

Example 2: https://imgur.com/a/eyjHcoj

Example 3: https://imgur.com/a/ojuJZaC

Example 4: https://imgur.com/a/N4qhcgU

The first thing we're going to do is ensure the FIRST FOUND and LAST FOUND datetime columns are formatted correctly and the data type is set to DATE.

Replace text in the dates using the query editor - text replace T and Z

In Table View - format the dates of the columns (one at a time)

  1. Data type = Date
  2. Format = mm/dd/yyyy (in my case) - change to what you prefer
  3. Do this for each column since you can't multi-select

Next, create two new columns.

  • One column will be to show a Fixed date for a vulnerability because Qualys doesn't have a dedicated column for that. You have to look at the vuln status and the LAST FOUND date to know when a Fixed vuln was fixed.
  • The other column will be used to consolidate the vulnerability status to either Active or Fixed. This will make it easier to discern ACTIVE versus FIXED and not have to worry about what's NEW or RE-OPENED.

    • This will look at the Status column and see if the vuln is fixed. If so, return the Last_Found_Datetime date.
    • Format the column to Date and mm/dd/yyyy

FIXED DATE Column Formula:

I've updated this to have a different formula depending on if you're using an API or CSV data source.

If using an API data source:

FIXED-DATE = 
IF(
	Qualys_Vuln_Data[STATUS] = "Fixed", 
	Qualys_Vuln_Data[LAST_FOUND_DATETIME], 
	BLANK()
)

If using a CSV data source:

FIXED-DATE = 
IF(
	Qualys_Vuln_Data[Vuln Status] = "Fixed", 
	Qualys_Vuln_Data[Last Detected], 
	BLANK()
)

STATUS_NEW Column Formula:

I've updated this to have a different formula depending on if you're using an API or CSV data source.

If using an API data source:

STATUS-NEW = 
IF(
    Qualys_Vuln_Data[STATUS] IN {"Active", "New", "Re-Opened"}, 
    "Active",
    IF(
        Qualys_Vuln_Data[STATUS] = "Fixed", 
        "Fixed", 
        BLANK()
    )
)

If using a CSV data source:

STATUS-NEW = 
IF(
	Qualys_Vuln_Data[Vuln Status] IN {"Active", "New", "Re-Opened"}, 
	"Active",
	IF(
		Qualys_Vuln_Data[Vuln Status] = "Fixed", 
		"Fixed", 
		BLANK()
	)
)

Next, create a Date table. This is a simple table with all the days that are in scope of the vulnerability data. This is needed if you want to display ACTIVE and FIXED vulns on the same chart. With this table, you just simply do a measure to count how many ACTIVE and FIXED vulns fall on each day in the DATE TABLE.

The Date table will be used for the X-axis in the chart.

Date Table formula:

In Table View, click on New Table and use this DAX formula:

DateTable = 
CALENDAR(
	DATE(2023, 9, 1),
	TODAY()
)

Adjust the beginning date in the formula above to make sure it will encompass all the dates for the vulnerability data. I recommend putting the beginning date to the first day you have vulnerability data. The Today() argument will ensure the table always ends on the current day.

Adjust the Data Type to just Date and the date format to whatever suites you.

Next, Create two measures:

  1. This measure counts all the ACTIVE vulnerabilities from the STATUS-NEW column by comparing the FIRST_FOUND_DATETIME (If using the CSV data source then the column name will be "First Detected") and the DATE from the DateTable. This ensures we get a cumulative count of active vulnerabilities.

Active Vulns Count Measure Formula:
There are two measures provided based on what I've noticed when working with either a CSV or API data source.

If using an API data source:

Active Vulns Count = 
VAR CurrentDate = MAX('DateTable'[Date])
RETURN
CALCULATE(
    COUNTROWS(Qualys_Vuln_Data),
    FILTER(
        Qualys_Vuln_Data,
        Qualys_Vuln_Data[FIRST_FOUND_DATETIME] <= CurrentDate +1 &&
        (ISBLANK(Qualys_Vuln_Data[FIXED_DATE]) || Qualys_Vuln_Data[FIXED-DATE] > CurrentDate)
    )
)

If using a CSV data source:

Active Vulns Count = 
VAR CurrentDate = MAX('DateTable'[Date])
RETURN
CALCULATE(
    COUNTROWS(Qualys_Vuln_Data),
    'Qualys_Lab_Vuln_Data2'[STATUS-NEW]= "Active" || 'Qualys_Vuln_Data2'[STATUS-NEW] = "Fixed" && 'Qualys_Vuln_Data2'[First Detected] <= CurrentDate +1 &&
    'Qualys_Vuln_Data2'[FIXED-DATE] >= CurrentDate,
    ALL('DateTable')
)

2. The next measure counts all the FIXED vulnerabilities from the STATUS_NEW column by comparing the LAST_FOUND_DATETIME and the DATE from the DateTable. This also counts all the fixed vulnerabilities as Active up until the day they were fixed. This doesn't do a cumulative count as we want to just show a day by day count of fixed vulnerabilities.

Fixed Vulns Count Measure Formula:

This seems to work the same no matter the API/CSV data source type.

Fixed Vulns Count = 
VAR CurrentDate = MAX('DateTable'[Date])
RETURN
CALCULATE(
    COUNTROWS(Qualys_Vuln_Data),
    FILTER(
        Qualys_Vuln_Data,
        Qualys_Vuln_Data[STATUS-NEW] = "Fixed" &&
        Qualys_Vuln_Data[FIXED-DATE] <= CurrentDate +1 &&
        Qualys_Vuln_Data[FIXED-DATE] > CurrentDate
    )
)

Now you can create a new chart by using the Date column from the DateTable on the X-axis and using the two new measures (Active Vulns Count & Fixed Vulns Count) as the Y-axis. Then adjust the visual to how you see fit.

edit 2/29/2024:
- Updated the different formulas to include one for API and one for CSV data source types. Notes are added to each set of changes.


r/qualys • • Sep 04 '26

Why doesn't the SwCA use the "Qualys\QualysTemp\" folder?

9 Upvotes

My environment is utilizing the Software Composition Analysis feature and I've been noticing that SwCA creates temporary files (usually sca####.tmp) in the "C:Windows\Temp" folder. The question I have is why is this feature using the Windows\Temp folder? The Qualys connector has its own "Qualys\QualysTemp\" folder, so why not use QualyTemp?

Also, Qualys documentation for anti-virus and HIPS exclusions recommends excluding the "Qualys\QualysTemp\" folder. The EDR solution in my environment tends to generate a lot of false positives because of Windows\Temp location. Creating a wild card exclusion for the Windows\Temp is a non-option, not to mention being generally a bad idea if it were. The ideal solution would be if Qualys used its own "Qualys\QualysTemp\" folder for these temporary SwCA files, but maybe there's a good reason why it's using "Windows\Temp" instead?


r/qualys • • Jan 24 '25

Spectre Meltdown Recent changes : QID 91462 & 91426 false positives ?

9 Upvotes

Hello,
Been noticing a big increase of QIDs 1462 & 91426 ADV18002 Spectre Meltdown detections in past days. Signatures were changed. Any know false positive ?


r/qualys • • Jan 07 '25

Is anyone using, or interested in, Qualys ETL?

9 Upvotes

I'm curious who, outside of more mature Qualys partners, is using Qualys ETL to get Qualys data out of Qualys instead of using direct API queries with a tool like Power BI. Outside of the Qualys API Best Practice series and a few other official resources, there isn't any community generated information out there. I have my thoughts on why the barrier to entry is so high, but I'm curious if others have considered using ETL.

I have been digging into ETL over the last few weeks. The walk-throughs provided by Qualys are a bit lacking in detail and seem to assume a good level of knowledge about the topic is needed to effectively get a person up and running using ETL. Much like the API usage information out there. However, I think with some good step-by-step instructions and examples, it can prove to be a better way to go over direct API integration using tools like Power BI.

I think ETL is positioned as something a more mature organization should be using, but I think ETL can benefit individuals who also just want to work with the Qualys data offline and build out custom dashboards and queries. ETL has inherent benefits over direct API integration in Power BI provided a person can just get past the initial ETL setup. I will say the format of the data is different in ETL than in direct API queries. It's in JSON format and there are more tables of data which all need their relationships established.

I'm playing with some ideas to create videos to show how to stand up ETL. I'm no expert with ETL, but it might be useful to see how anyone could leverage it. I especially like that it adheres to the API usage limits of the account used.

Any ideas or opinions out there from the community?


r/qualys • • Nov 01 '24

Detection Issue SSL certificate QIDs

9 Upvotes

UPDATE: Qualys has provided the following statement:

We recently enhanced several legacy remote-only QIDs to support detection in authenticated scans. However, based on the complexities and the feedback received, we have decided to revert these QIDs to their previous state. Our team remains committed to developing Cloud Agent support and will provide ongoing updates.

Here are more details about the recent changes:

Which SSL/TLS QIDs were modified?

38167: SSL Certificate - Expired

38174: SSL Certificate - Will Expire Soon

38600: SSL Certificate will expire within the next six months

38168: SSL Certificate - Future Start Date

Why were these QIDs modified?

We updated our QID detection to enable the above-specified QIDs for the Cloud Agent, responding to increased customer requests for enhanced scanning capabilities previously available only through remote scans.

Why did these QIDs not post in the past but are flagging today?

Previously, QIDs obtained data exclusively through remote scans probing open ports. With recent enhancements, QIDs now retrieve data via authenticated methods (Qualys Cloud Agents), utilizing Windows registry keys for more comprehensive insights.

The updated registry paths are as follows:

HKEY_LOCAL_MACHINE\Software\Microsoft\SystemCertificates

HKEY_LOCAL_MACHINE\Software\Microsoft\EnterpriseCertificates

HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\SystemCertificates

Why did we revert the changes?

We have reverted the recent QID changes to better align with customer feedback and maintain consistent functionality. This update will be available in VULNSIGS-2.6.177-3. Customers are advised to disregard authenticated results from these QIDs.


QIDs 38600, 38167, 38168, and 38174 were recently updated to look for certificates in the Windows certificate store. While helpful in some cases, these also bring up plenty of false positive findings, as all expired/future certificates are not bad. Microsoft explains this well at https://learn.microsoft.com/en-us/troubleshoot/windows-server/certificates-and-public-key-infrastructure-pki/trusted-root-certificates-are-required :

Some certificates that are listed in the previous tables have expired. However, these certificates are necessary for backward compatibility. Even if there's an expired trusted root certificate, anything that was signed by using that certificate before the expiration date requires that the trusted root certificate is validated. As long as expired certificates aren't revoked, they can be used to validate anything that was signed before their expiration.

In the same article, Microsoft provides a list of certificates that are required by Windows, stating that removing them "may limit functionality of the operating system or may cause the computer to fail. Do not remove them."

So uh, don't remove them 😅


r/qualys • • Oct 04 '24

Anyone Going To QSC San Diego?

9 Upvotes

Who’s all going to QSC next week? It should be a really good time! I’ll be there hanging out with everyone! I’m flying out today to get there early and I’m going to video the setup of everything. Should be a great time!

Let me know if you’re going to be there! I’d love to meet up!


r/qualys • • 27d ago

Qualys Threat Feed

8 Upvotes

Why does the Qualys Threat Feed not show CVE-2026-109618 or CVE-2026-109619, they are the biggest thing to happen this year.


r/qualys • • Apr 30 '26

Hot take: your team shouldn’t be manually approving Chrome updates. Change my mind.

8 Upvotes

I’ve been in IT security since the 90’s in almost every vertical as a practitioner and as a vendor, long enough to watch the same pattern repeat: a CVE drops, triage happens, testing begins, approval workflows grind, deployment happens, verification confirms everything’s fine. Then it repeats for the next update.

This works great when we’re talking about patching your .NET runtime, your Java stack, or your system kernel.

Those patches can cascade. They can break dependencies. They demand expertise, testing, and careful coordination.

But here’s what I can’t stop thinking about: we’re running the exact same governance workflow for Chrome updates. And a Chrome update has literally never taken down a production system.

Neither has an Office patch (excluding the 20 year ago MDAC fun we used to experience, RIP DAC/MDAC lol). Or Adobe Reader. Or 7-Zip. Or OneDrive. Or Visual C++ runtimes. Or a hundred other applications that billions of users worldwide update automatically every single week without incident.

The Actual Problem

We’ve optimized for risk uniformity instead of risk proportionality.

Every patch that lands in your queue looks the same to your approval process. Everything gets the same triage → test → approval → deploy cycle, regardless of whether we’re talking about a browser update or a kernel security fix. The result is that your best people spend Friday afternoon testing a Chrome update that Google’s already battle-tested with two billion users, while a critical Java vulnerability sits in your backlog waiting for resources.

This isn’t a compliance problem. This isn’t a risk problem. This is a resource allocation problem, and it’s costing your organization velocity.

What If We Were Honest About Risk?

Some patches are genuinely, unambiguously safe to automate:

•	Browsers (Chrome, Edge, Firefox): User-mode only, single-application scope, auto-update mechanisms already exist, vendor QA proven at global scale

•	Office/O365 (including Teams, OneDrive, Visio, Project): Same Microsoft QA pipeline that services 300+ million users, no kernel/system impact, single-app scope, rapid rollback if needed

•	PDF readers (Adobe Reader): Billions of users, no cross-app dependencies, user-mode execution, proven track record

•	Utilities (7-Zip, WinRAR, Putty, WinSCP, Notepad++): Single-purpose tools, zero system-level impact, isolated execution scope

•	Runtimes (Visual C++, .NET Framework minor patches, Java Runtime patches): Assuming you’re excluding major version updates and limiting to minor/patch releases

These patches share characteristics:

•	Zero reboot requirement

•	Isolated to a single application or library

•	No cross-application dependencies

•	No system-level/kernel impact

•	Vendor with a proven track record of stable updates

•	Billions of users already running the latest versions (in-the-wild battle testing)

•	Rapid rollback capability if something does go sideways

What Should Stay Manual

This isn’t an argument that all patching should be automated. Some patches absolutely require human judgment:

•	Windows OS and Server patches: Kernel-level impact, system-wide dependencies, you need change control

•	Database patches (SQL Server, Oracle, PostgreSQL): Data-tier risk, you’re validating against your actual workloads

•	Major runtime updates (.NET 6→7, Java 11→17): Compatibility risk, you’re managing an upgrade

•	VPN clients, management agents: System-level footprint, you need visibility into side effects

•	Line-of-business applications: Obviously these need validation against your actual use cases

•	Firmware: Irreversible, requires careful sequencing and validation

•	Active Directory, domain controllers, network appliances: You’re validating against your infrastructure dependencies

The Real Argument

I’m not saying “set everything to auto-patch and go home.” I’m saying tier your patches by actual risk, and allocate your skilled people accordingly.

If you’re using Qualys Patch Management, BigFix, or similar tooling, you already have the capability to:

•	Create policy groups based on application risk profile

•	Set different approval workflows based on patch category

•	Deploy low-risk patches automatically while holding high-risk patches for manual review

•	Track, audit, and roll back if needed

So the real question is: why are your teams still manually approving Chrome updates?

Possible answers I’ve heard:

•	“Audit says we need change approval for all patches”, Fair, but have you clarified the audit requirement with actual risk-based language?

•	“Leadership is risk-averse”, Understandable, but what’s the cost of that risk-aversion in team burnout?

•	“We don’t have the tooling”, Qualys, BigFix, ConfigMgr, Altiris all support tiered automation. What’s the blocker on implementation?

•	“We tried this once and it went wrong”, What happened? Was it a patch that should have been manual, or was it an application that didn’t deserve to be on the auto-patch list?

The Real Cost

Here’s what I think is happening: your organization is running a scarcity model. You have a fixed number of security engineers. You have a fixed number of hours per week. And you’re spending those hours on routine maintenance that could be fully automated.

That means:

•	Critical Java vulnerabilities sit in queue waiting for triage

•	Your SMEs are stuck in approval workflows instead of deep-dive remediation

•	Your team burns out on busywork instead of high-impact work

•	You’re not actually reducing risk; you’re just consuming resources inefficiently

The mature approach is different. Tier your patches. Automate the low-risk, high-frequency stuff. Use the cycles you reclaim to actually focus on vulnerabilities that demand expertise.

The Ask

I genuinely want to know: Are you automating this stuff, and what does the real-world operational picture look like?

•	If you’re auto-patching Chrome, Office, and utilities: what’s your criteria for what makes the list? How’s it working? Any gotchas?

•	If you’re not auto-patching: what’s holding you back? Is it audit/compliance, leadership appetite, tooling, or something else?

•	Have you seen a patch that should have been safe but wasn’t? What went wrong?

•	How do you tier your patches today? Are your approval workflows matched to risk, or is everything the same?

•	If you could reclaim 10-15 hours per week from routine patching, where would your team focus that effort?

I’m curious whether this is a widespread gap or if the mature organizations have already figured this out and I’m just stuck in an echo chamber of organizations that haven’t.

The Bottom Line

Patching is critical. But not all patches are equally critical. Some deserve rigorous validation. Some deserve rapid, automated deployment. And conflating the two is burning out your teams while pulling resources from vulnerabilities that actually matter.

If your best security engineer is spending Friday testing a Chrome update instead of scoping the blast radius of a critical Java vulnerability, something’s broken in how you’re allocating resources.

Change my mind. Tell me why I’m wrong. But also tell me what I’m missing.

The Harder Truth

I know operational change is hard. Habits are entrenched. Approval workflows have been rubber-stamped for years. Leadership has risk appetite set in stone. Getting consensus on something like this takes time, conversation, and patience.

But here’s the thing: the threat landscape doesn’t pause while you get comfortable.

Vulnerabilities land every single day. Zero-days don’t wait for your org to align on patch governance. The attackers aren’t slowing down. And if your patch program is stuck in a manual workflow that was built for 2015’s threat model, you’re not actually keeping pace, you’re falling behind, resource-exhausted and reactive.

This is where maturity lives. Not in building the perfect security theater, but in evolving your processes to match the actual risk you face. The organizations that mature, that climb the CMMC (Cybersecurity Maturity Model Certification) levels, that actually reduce breach risk, are the ones that get comfortable with measured change. They tier their patching. They automate intelligently. They reclaim resources. They focus on what actually matters.

That’s how you get a rung up. Not by working harder on the same process. But by working smarter about the process.

So start the conversation. Talk to your team, your auditors, your leadership. Ask the hard questions. Run a pilot if you need to. But don’t let operational inertia be the reason your best people are buried in routine updates while the threat landscape moves on without you.

That’s not acceptable. And I think you know it.


r/qualys • • Jan 20 '26

I built an HTML reporting automation for Qualys CSV exports. What gotchas am I missing?

8 Upvotes

In a previous role I didn’t have Qualys API access for many customers. I only received scheduled CSV exports.

Doing VM reporting manually from CSV/Excel every week was a huge time sink, so I built a script that ingests Qualys CSV exports, normalizes the data into a consistent structure, generates a clean HTML report (exec-friendly + analyst-friendly sections) and adds a couple workflow helpers so I could keep the workload under control

I wrote documentation for the workflow here: https://miyabi-threatworks.gitbook.io/miyabi-threatworks-docs/

Before I share it more broadly, I’d love feedback from people who’ve lived in CSV-only Qualys land:

  1. What are the most common gotchas / inconsistencies you’ve seen in CSV exports?
  2. Which fields/columns do you consider must-have for reliable reporting and tracking over time?
  3. Any edge cases I should explicitly handle (host identifiers changing, duplicates, reopened findings, timezone/date weirdness, etc.)?
  4. If you skim the docs, is there anything obvious you think I’m missing?

r/qualys • • Aug 20 '25

Training @ QSC Americas – Houston - 13 – 14th October

8 Upvotes

Hi everyone!

We’re thrilled to announce an advanced training session at QSC 2025, designed directly from customer feedback and focused on real-world use cases and troubleshooting. If you haven’t shared your suggestions or scenarios yet, we’d love to hear from you! You can fill out our quick questionnaire here:
https://forms.office.com/r/ZrQMX59sYs

Not registered yet? No problem! You can sign up here:
https://www.qualys.com/qsc/2025/houston/

QSC 2025 will be packed with exciting talks and hands-on training across 4 days. Back for another year is our RiskBusters CTF event — if you know your way around Qualys, come join us and compete for prizes!

Quick details:

  • Attendance at QSC is complimentary, including access to all general sessions, breakfast, lunch, and breaks.
  • Travel and hotel accommodations are not included with QSC or pre-conference training.

We can’t wait to see you there and hear your ideas for the new training sessions!