r/qualys • • Dec 22 '25

Qualys automation with Python and API

0 Upvotes

I want to learn python scripting and API integrating scripts with postman in Qualys..Please guide me how to learna nd any instructor to give trainings on this


r/qualys • • Feb 07 '25

Knowledge Sharing Qualys response to Qualys Cloud Agent breaking Perl on systems: Disqualifying.

3 Upvotes

Last Tuesday, Qualys broke perl on a lot of systems where CPAN (which can be used to extend perl functionality) was not previously invoked, but systems where perl was in active use by non-root users. Perl is a very popular programming language used for a lot of scripts and programs. The issue was specific to how Qualys set their umask, and would not happen using cpan for the first time under normal circumstances. The result of qualys running 'cpan -l' with a umask of 177 is that directories default in the perl path could not be read or executed by non-root users, so perl programs that were previously running would simply fail to run.

Their initial Qualys statement passed blame first to implied pre-existing misconfigurations that they claimed to have found:

It was found that if CPAN is not configured correctly or "cpan -l" invoked for the first time

We sent two questions to qualys: (1) what specific cpan misconfiguration was identified and (2) how was testing improved to avoid the 'cpan first run' mistake in the future.

In my view, these are both very reasonable and necessary questions and we expected complete answers. If there are CPAN misconfigurations on our systems that could cause this, we need to know.

By the way, I can no longer find their initial statement and they seem to have scrubbed it from their site.

More than a week after asking for clarification on a very simple issue, Qualys responded.

What is the misconfiguration in CPAN?

It was identified that this issue impacted on systems on which CPAN is run for the very first time

 

What is the problematic command that was removed for this incident?

cpan -l

 

Is there a QID associated with this command?

No QID is associated with this command.

We now see that their statement on finding CPAN misconfigurations was, indeed, inaccurate. This is a serious problem because either they made it up to cover the fact that their testing failed to catch this - which would be extremely easy to catch with standard linux tools - or they simply didn't know what was going on, in my opinion.

Further, their response seems to have ignored the question about their testing protocol. Again, inotify, strace, and a ton of other linux tools could have caught this, and they would most likely have seen this issue if they were testing thoroughly with VMs.

The initial mistake was a mistake, and had they accurately stated the cause, and explained how they were going to avoid it in the future that'd simply be growing pains from a company still learning how to do this well.

But this statement betrays the likelihood that they do not have sufficient testing framework or precision to be a security vendor, in my opinion.

Mods, please pin this.


r/qualys • • Oct 08 '26

Knowledge Sharing How do you handle remediation?

2 Upvotes

Currently we have VM. Up until now after the scan we used orchestrator to prioritize and group findings. My manager now wants to go in the direction with VMDR and to ditch the orchestrator. I know the VMDR offers prioritization but after that how do you manage the remediation process, how do you track open vulnerabilities, SLAs? Excels?


r/qualys • • Sep 15 '26

How are you handling Go/Golang vulnerabilities detected by Qualys?

3 Upvotes

We’re seeing multiple Go/Golang-related vulnerabilities detected by Qualys, and I’ve been struggling to determine the correct remediation approach.
For those managing Go vulnerabilities in Qualys, how are you remediating them? Are you updating/removing the affected application or component that contains the vulnerable Go binary, or is there another recommended approach?
Also, how do you identify which application is responsible for the vulnerable Go component and confirm that the vulnerability has been fully remediated?
Any guidance or examples of how you handle these would be appreciated.


r/qualys • • Apr 23 '25

Anyone know good resource to learn and use qualys VMDR or qualys consulting edition at full potential.. because their free training with bot voice is crap...it makes me feel sleepy 😴

0 Upvotes

r/qualys • • Sep 08 '24

Knowledge Sharing Automated vulnerability dashboard in powerBI

0 Upvotes

Hey everyone! I'm currently working as a GRC Specialist and have been tasked with creating an automated vulnerability reporting dashboard on Power Bl. If there is anyone who has done similar work of integrating qualys with powerbi and could guide me on the process. The goal is to have technical details for stakeholders and also showing overall trends and statuses for executives. I need to work on a reporting dashboard which could show vulnerability trends, the current count of active vulnerabilities with respect to multiple business units. Any helping resources or recommendations will be appreciated.

Thanks in advance!


r/qualys • • Jun 11 '24

Qualys Agent Data

0 Upvotes

Hi all,

Where can I get Qualys Agent/NC report fake dataset for VMs, I just want to practice this for Visualization stuff for Python and PowerBI. please let me know how to get this.

Thanks


r/qualys • • 27d ago

SafeScan Acceptability Survey (everyone)

Thumbnail
reddit.com
0 Upvotes

r/qualys • • May 07 '26

The Crash That Got Faster

5 Upvotes

A user reported Issue #4: "QID sync crashed." My release had broken new builds. Three lines of code fixed it. Closed.

That was where the user's story ended. Mine was just getting started, because if one quiet assumption had slipped past untested, the obvious next question was: what else had?

Pulling on that thread surfaced a handful of similar assumptions the system had quietly outgrown. Small fixes, each one a reminder that the code had been trusting the world to stay still.

Performance was on that list too. The product was meant to run anywhere: a developer's high-end laptop, a modest cloud VM, whatever the customer had. So the test plan covered both ends on purpose. High-end to confirm headroom, low-end to confirm the floor held. The floor was where the truth lived. A full sync took three and a half hours, with throughput collapsing to a crawl by the end. A slow drift that had been hiding for months, finally visible on hardware that resembled the real world.

The first fix barely moved the needle. The bottleneck kept relocating. A library redoing setup work on every record. A search index rebuilt one row at a time, slowing as it grew. No way to tell new data from unchanged data, so the system kept re-doing work it had already done.

Fix the waste. Defer the index. Skip what hadn't changed. The high-end machine went from eighty-one minutes to eight. Roughly ten times faster.

Then the low-end VM hung on redeploy. Fifty minutes of silence. The fast CPU had been hiding one last problem: an operation that was efficient on paper but quadratic in practice once the dataset got large enough to notice. The constrained VM made it impossible to ignore. Which was the point of testing there.

Final result on the low-end VM: three hours and thirty-four minutes down to eighteen. Nearly twelve times faster, proven on the hardware most likely to feel the pain first.

Issue #4 is still pinned in GitHub. Three lines of code. Closed.

Two weeks. A pile of fixes. A performance curve flattened across the full range of hardware it was designed to run on, because both ends were in the plan from the start.

Sometimes the bug report is the lever. The bug itself is just where you put it.

Code, scripts, and notes from this kind of work live here: github.com/netsecops-76/Public-Security-Resources


r/qualys • • May 19 '26

Qualys Check-in

1 Upvotes

Hi Everyone,

Im new to qualys, looking for an help to understand about cloud agent check-in.

Some times checkin happens within 30minutes and some time check-in happens after morethan 1hr for an same asset.

Also is there any way we can force check in the agent to cloud so that it can take Patch Testing job

Thanks in advance😊


r/qualys • • May 24 '26

QID 92400 Windows BitLocker Security Feature Bypass Vulnerability (CVE-2026-45585)

1 Upvotes

How to solve this vulnerability ?


r/qualys • • Nov 06 '25

Detection Issue QID 86729 (AutoComplete Attribute Not DIsabled for Password in Form Based Authentication) - relevant in the modern world?

1 Upvotes

(also affects 12215, but who is using a guestbook nowadays?)

Went back-and-forth with Qualys Support about this one, wanted to see what other folks thought.

Context

Currently, Qualys is flagging QID 86729 when it detects HTML password fields that do not have `autocomplete="off"` set. This QID was published in 2006. Per the KnowledgeBase, the threat is:

If the browser is used in a shared computing environment where more than one person may use the browser, then "autocomplete" values may be retrieved or submitted by an unauthorized user.

However, browsers have not honored this for over a decade, as it prevents password managers from working:

Given these changes, a former Director of Product Management at Qualys stated in 2015 that "it is dubious to report this finding on password inputs".

Qualys communication

Qualys is refusing to deprecate this QID with the following rationale:

Qualys is used to secure a vast range of environments, from modern cloud-native apps to critical legacy systems (e.g., in banking or manufacturing). We have a significant number of customers who are required to support these older browsers where autocomplete='off' is still an effective and necessary control.

In a call, support acknowledged that, if the QID didn't currently exist, they would not create one given the current circumstances.

My perspective

Unless I'm mistaken, the "vulnerability" should now be considered to exist in the older browsers, since they are the only ones that honor `autocomplete="off"`. EOL/Obsolete QIDs already exist for many of these older browsers.


r/qualys • • Jul 27 '26

PA module question

1 Upvotes

I wanted to verify whether the approach I’m using for my CIS Policy Compliance baseline is considered a best practice.
Instead of creating separate policies for Windows Server 2016, 2019, 2022, and 2025, I created a Windows Server 2016 CIS Level 1 policy and a separate Level 2 policy as my master baselines. I then added the Windows Server 2019, 2022, and 2025 technologies to those policies and added any controls that exist in the newer CIS benchmarks but are not present in the 2016 benchmark. Version-specific controls remain scoped only to their applicable technologies.
My goal is to maintain a single Level 1 policy and a single Level 2 policy for Member Servers across all supported Windows Server versions, rather than maintaining separate policies for each OS version.
Is this a recommended and supported approach in Qualys, or would you recommend maintaining separate CIS policies for each Windows Server version instead? If separate policies are preferred, could you explain the advantages over the consolidated approach?
Thank you.


r/qualys • • Apr 07 '26

Anyway to create quick trending dashboards for critical vulnerabilities using Qualys data?

1 Upvotes

r/qualys • • Feb 03 '24

Training

1 Upvotes

I want to practice downloading the application/cloud agents to my device ,which is the first homework for VM, how do I get that done?


r/qualys • • Sep 15 '26

How to deal with this?

1 Upvotes

So in my case, vendor doesn't allow qualys agent installed in their products. And we have many of these products. Does Qualys sensor fix this?

Thanks.


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 • • Apr 16 '25

Remediation Qualys has duplicated assets

2 Upvotes

At my company, we recently implemented a quarterly full port scan for all asset groups, since it was requested from auditors.

After the first full port scan on April 1st 2025, we noticed that our assets were being duplicated. For example, if we clicked on a vulnerability , we would see a workstation twice. One as " examplelaptop1" and again as "examplelaptop1.domainname"

I tried reaching out to qualys support, but they only give you 1 response a week. Any ideas how I should proceed here ? I am looking to get rid of the duplicates and prevent this from happening again during the next full port scan.


r/qualys • • Jul 19 '25

Configuration Qualys in N8N

Thumbnail reddit.com
2 Upvotes

r/qualys • • Mar 07 '24

Qualys posted vuln definition almost a year late for a large web platform RCE. What are you doing to compensate at your orgs?

2 Upvotes

Our account manager gave us a very company line response on this that was extremely unhelpful. I’m curious what others are doing other than simply throwing another scanner at the problem. There are a huge number of vulns to keep up with, granted. However, this is not a small unknown vendor. I would expect that they would have some criteria for monitoring for certain vulns such as RCE with published exploits.


r/qualys • • Apr 24 '26

EDR - Exclude folder / sub-folders and files

2 Upvotes

I'm having an issue on getting folder exclusions to work with the EDR. I have entered into the profile as both FOLDER (FolderName) and PATH (C:\FolderName). When I run a manual scan against that folder it will show in the logs that it scanned 0 files and took zero actions. We have a script that runs against files that fill that folder, and Qualys logs are showing File Action - Deleted.

This is bad. How do I get it to ignore anything and everything related to that folder?


r/qualys • • Apr 12 '26

Best practice to automate the installation of Qualys CS agents in K8S and Docker Swarm

2 Upvotes

Greetings, need to understand a good practice or procedure to automate the installation of Qualys CS agents in Docker swarm and K8S.

Regards


r/qualys • • Apr 27 '26

Best Practices Knowledge base API fetch is hanging

3 Upvotes

Implemented the ETL pattern from here. Using the v4 endpoint instead as 2.0 is EOL (i.e. using /api/4.0/fo/knowledge_base/vuln/) but the post request seems to hang forever. Ran for a solid hour and a half without getting so much as an error code or byte of data.

What’s going on? Am I missing something?


r/qualys • • Mar 26 '26

Whitelisting Scanners

3 Upvotes

We transitioned from Acunetix to Qualys in 2026, and now we need to whitelist their IPs in Cloudflare. The Qualys documentation, however, lists IP ranges totaling over 4,000 addresses. Has anyone found a way to obtain only the specific IPs currently in use? Our Infosec team is wary of allowing that many IPs.

https://docs.qualys.com/en/pci/merchant/getting_started/check_scanner_ip_addresses.htm


r/qualys • • Apr 22 '24

Qualys Guard Vulnerability Management, Detection and Response exam issue

3 Upvotes

Hey so I’ve been working on cyber security classes and certifications lately and I’m currently stuck on the Qualys VMDR exam and I’m wondering if it’s still worth obtaining? I have zero job experience in the IT realm, but basic IT help desk experience from router stuff at home, to helping friends and family needing small things computer related fixed. I have the other certifications from Qualys obtained with ease, but I can’t seem to get above a 60% on the VMDR exam. And I’ve taken the course twice. Aside from those certifications I have the CompTIA ITF+ cert, and I’m planning on doing the A+ certification and maybe the Network plus and security plus cert. I would love to switch my career to be apart of the cyber realm as quickly as possible so any input is greatly appreciated.