<!-- mobian-agent-page publisher="dailydev" canonical="https://daily.dev/posts/reducing-shadow-it-visibility-gaps-with-wazuh-ama35kdaz" -->

---
title: Reducing shadow IT visibility gaps with Wazuh | daily.dev
description: Shadow IT—unmanaged endpoints, unapproved applications, and devices outside standard monitoring—creates blind spots that network discovery scans alone cannot...
canonical: https://daily.dev/posts/reducing-shadow-it-visibility-gaps-with-wazuh-ama35kdaz
twitter:card: summary_large_image
twitter:site: @dailydotdev
og:type: website
og:site_name: daily.dev
og:title: Reducing shadow IT visibility gaps with Wazuh | daily.dev
og:description: Shadow IT—unmanaged endpoints, unapproved applications, and devices outside standard monitoring—creates blind spots that network discovery scans alone cannot...
og:url: https://daily.dev/posts/reducing-shadow-it-visibility-gaps-with-wazuh-ama35kdaz
og:image: https://api.daily.dev/og/posts/aMA35kdaz.png
og:image:alt: Reducing shadow IT visibility gaps with Wazuh
og:image:width: 1200
og:image:height: 630
og:locale: en
---

> ## Documentation Index
> Fetch the complete documentation index at: https://daily.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# Reducing shadow IT visibility gaps with Wazuh

**[BleepingComputer](https://daily.dev/sources/bleepingcomputer)** · 6 min read · 0 upvotes · 0 comments

## Summary

Shadow IT—unmanaged endpoints, unapproved applications, and devices outside standard monitoring—creates blind spots that network discovery scans alone cannot close, since scans only detect what responds during a scan window. Wazuh, an open source SIEM and XDR platform, addresses this through continuous endpoint inventory collection (hardware, software, browser extensions, services, ports), agentless SSH monitoring and syslog ingestion for devices that cannot run an agent, and correlation of inventory data against vulnerability and end-of-life software databases. Agent enrollment states (never connected, pending, active, disconnected) help teams measure actual monitoring coverage rather than assume it, and custom rules with Active Response scripts can detect and remove unauthorized applications automatically.

## Full article

daily.dev links to this article rather than hosting it. Read it at the original source: <https://www.bleepingcomputer.com/news/security/reducing-shadow-it-visibility-gaps-with-wazuh>

## Questions this post answers

### What data does the Wazuh agent collect for system inventory monitoring?

The Wazuh agent collects hardware details, operating system information, installed packages, network interfaces, listening ports, running processes, services, users, groups, and browser extensions from each monitored endpoint, with Windows agents also reporting installed updates. This system inventory capability is enabled by default, runs an initial scan on agent startup, and rescans on a configurable interval defaulting to one hour.

_Teams evaluating endpoint visibility tools can follow ongoing Wazuh coverage on daily.dev._

### How can I monitor network devices like routers and switches that cannot run a security agent?

Wazuh provides agentless monitoring over SSH for routers, firewalls, switches, and Linux or BSD systems, while devices supporting neither an agent nor SSH can send data via syslog directly to the Wazuh server. These methods extend visibility to devices that cannot run a Wazuh agent, though they only surface information exposed by configured commands, files, and logs.

_daily.dev helps security practitioners track agentless monitoring approaches like this one._

### What are the possible states of a Wazuh agent and what do they mean?

A Wazuh agent can be in one of four states: never connected, pending, active, or disconnected. Never connected or pending states indicate deployments that did not complete, while an agent moves to disconnected when no keep-alive message arrives within a configurable window that defaults to 15 minutes, helping teams find endpoints assumed to be monitored but not actually reporting.

_Security teams tracking monitoring coverage gaps can follow related tooling updates on daily.dev._

## Similar posts on daily.dev

- [The IT Asset Inventory Problem](https://daily.dev/posts/the-it-asset-inventory-problem-yao39moac) · Arctic Wolf · 0 upvotes · 0 comments
- [The Risks of Shadow APIs: How Unmanaged Endpoints Bypass Your CI/CD Checks](https://daily.dev/posts/the-risks-of-shadow-apis-how-unmanaged-endpoints-bypass-your-ci-cd-checks-xwozlepe3) · Nordic APIs · 1 upvotes · 0 comments
- [Shadow IT Exists Because You Don't Control Which Devices Get Identity](https://daily.dev/posts/shadow-it-exists-because-you-don-t-control-which-devices-get-identity-opdh4cx1i) · Smallstep · 0 upvotes · 0 comments
- [Introduction to SIEM and Wazuh: Architecture, Components & Why It Matters](https://daily.dev/posts/introduction-to-siem-and-wazuh-architecture-components-why-it-matters-nduuaiso9) · InfoSec Write-ups · 1 upvotes · 0 comments

---

Tags: [#security](https://daily.dev/tags/security)

[View this post on daily.dev](https://daily.dev/posts/reducing-shadow-it-visibility-gaps-with-wazuh-ama35kdaz)

```json
{"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]}
{"@context":"https://schema.org","@type":"TechArticle","headline":"Reducing shadow IT visibility gaps with Wazuh","url":"https://daily.dev/posts/reducing-shadow-it-visibility-gaps-with-wazuh-ama35kdaz","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/reducing-shadow-it-visibility-gaps-with-wazuh-ama35kdaz"},"datePublished":"2026-09-22T17:22:50.531Z","dateModified":"2026-09-22T17:23:12.114Z","description":"Shadow IT—unmanaged endpoints, unapproved applications, and devices outside standard monitoring—creates blind spots that network discovery scans alone cannot...","image":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/874746951fbc770a43988e7ce03473fc?_a=AQAEuop","thumbnailUrl":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/874746951fbc770a43988e7ce03473fc?_a=AQAEuop","isAccessibleForFree":true,"articleSection":"BleepingComputer","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"BleepingComputer","logo":"https://media.daily.dev/image/upload/s--as8nJ3qy--/f_auto,q_auto/v1774959951/logos/bleepingcomputer?_a=BAMAMiWQ0","url":"https://daily.dev/sources/bleepingcomputer"},"commentCount":0,"discussionUrl":"https://daily.dev/posts/reducing-shadow-it-visibility-gaps-with-wazuh-ama35kdaz","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":0},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"security","timeRequired":"PT6M"}
{"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"BleepingComputer","item":"https://daily.dev/sources/bleepingcomputer"},{"@type":"ListItem","position":3,"name":"Reducing shadow IT visibility gaps with Wazuh"}]}
{"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/reducing-shadow-it-visibility-gaps-with-wazuh-ama35kdaz#faq","mainEntity":[{"@type":"Question","name":"What data does the Wazuh agent collect for system inventory monitoring?","acceptedAnswer":{"@type":"Answer","text":"The Wazuh agent collects hardware details, operating system information, installed packages, network interfaces, listening ports, running processes, services, users, groups, and browser extensions from each monitored endpoint, with Windows agents also reporting installed updates. This system inventory capability is enabled by default, runs an initial scan on agent startup, and rescans on a configurable interval defaulting to one hour. Teams evaluating endpoint visibility tools can follow ongoing Wazuh coverage on daily.dev."}},{"@type":"Question","name":"How can I monitor network devices like routers and switches that cannot run a security agent?","acceptedAnswer":{"@type":"Answer","text":"Wazuh provides agentless monitoring over SSH for routers, firewalls, switches, and Linux or BSD systems, while devices supporting neither an agent nor SSH can send data via syslog directly to the Wazuh server. These methods extend visibility to devices that cannot run a Wazuh agent, though they only surface information exposed by configured commands, files, and logs. daily.dev helps security practitioners track agentless monitoring approaches like this one."}},{"@type":"Question","name":"What are the possible states of a Wazuh agent and what do they mean?","acceptedAnswer":{"@type":"Answer","text":"A Wazuh agent can be in one of four states: never connected, pending, active, or disconnected. Never connected or pending states indicate deployments that did not complete, while an agent moves to disconnected when no keep-alive message arrives within a configurable window that defaults to 15 minutes, helping teams find endpoints assumed to be monitored but not actually reporting. Security teams tracking monitoring coverage gaps can follow related tooling updates on daily.dev."}}]}
```

