Skip to main content
Storage & files

Network Shares

Find SMB shares on Windows devices that are open to Everyone, Authenticated Users, Anonymous Logon or Guests.

The Network Shares check lists every SMB share on a Windows device together with its share permissions and the NTFS permissions of the shared folder, and alerts when a share is open to Everyone, Authenticated Users, Anonymous Logon or Guests. Open write access always raises a critical alert; open read-only access raises a warning you can switch off. The check runs on the device through the octoja agent and reads everything locally with the SMB tooling built into Windows — nothing is installed and no credentials are needed. It runs every 12 hours by default.

Prerequisites

  • The check runs on Windows only — client editions from Windows 8, server editions from Windows Server 2012. Those releases ship the SMB tooling the check reads shares and permissions with; on an older Windows the check reports the Get-SmbShare message below instead of a status.

Steps

  1. Go to Devices and open the Windows device.
  2. Click the Checks tab → Add Check → Network Shares.
  3. Adjust the settings if needed.
  4. Click Add Check.

Settings

All fields are optional — the check runs with its defaults out of the box.

FieldTypeRequiredDefaultDescription
Include admin sharesToggleNoEnabledAlso list the default admin shares (C$, ADMIN$, IPC$, …).
Shares excluded from alertingList of share namesNoSYSVOL, NETLOGONThese shares are still listed but never raise an alert (wildcards allowed). On domain controllers, read access for Authenticated Users on SYSVOL and NETLOGON is by design.
Warn on read-only open accessToggleNoEnabledAlso raise a warning when Everyone, Authenticated Users, Anonymous or Guests only have read access. Write access always raises a critical alert.
Query timeout (seconds)NumberNo120Maximum time to wait for enumerating the shares and reading their permissions. Appears only after enabling Show advanced options.
  • The printer-driver share PRINT$ also counts as an admin share. Turning off Include admin shares removes these shares from both the list and evaluation. A custom hidden share such as Data$ remains monitored: a trailing $ alone does not make it an admin share. To keep PRINT$ visible without raising alerts, leave admin shares enabled and add PRINT$ to Shares excluded from alerting.
  • Wildcards work in Shares excluded from alerting — Backup* matches every share whose name starts with Backup, and ? stands for a single character. Names are matched without regard to upper or lower case. Excluded shares stay in the list with the Excluded from alerting chip; they never change the check result.
  • Query timeout (seconds) has a floor of 30 seconds: values from 1 to 29 are raised to 30 when the check runs, and 0 falls back to the default of 120.

Results

Share permissions and NTFS permissions are evaluated separately. The check does not calculate their combined effective access. Restrictive NTFS permissions therefore do not cancel an alert for Change access granted to Authenticated Users on the share. Do not change a share to read-only just to clear the check if users need write access.

For intentional exceptions, use Shares excluded from alerting. A single * matches all shares and keeps their permissions visible, but suppresses all per-share findings: share permissions, NTFS permissions, and failures to read those permissions. This is not a switch for share-permission alerts alone. Monitor the excluded permissions another way; failures of the overall query can still produce an error.

The check result is the worst result across all shares. Open means access for Everyone, Authenticated Users, Anonymous Logon or Guests.

ResultWhen it happens
OKOutside the excluded shares, none of the four principals has access to any share or its folder.
WarningOne of the four principals has read-only access (only while Warn on read-only open access is enabled), or a share's permissions could not be read — Share “…”: share permissions could not be read. / Share “…”: NTFS permissions could not be read.
CriticalOne of the four principals has write access on the share itself or in the NTFS permissions of its folder. These rights count as write access: Full, Change, Modify, Write, Delete, TakeOwnership, ChangePermissions, CreateFiles, CreateDirectories and AppendData.

Deny entries never raise an alert: an entry that denies one of the four principals access restricts the share rather than opening it. It stays visible in the permission list, marked Deny.

What the check reports

Every run produces one card per share, with any findings collected above the list.

  • A summary line showing how many shares were checked and how many of them have open permissions. On a device with no shares to list, it reads No shares found. instead.
  • A list of findings, one line per open permission in the form Share “…”: share permission “…” for … — or NTFS permission for rights set on the shared folder.
  • One card per share with its name, file path and an OK, Warning or Critical badge; admin shares carry an Admin share chip, excluded shares an Excluded from alerting chip. Cards fold open and shut; those with a warning or critical result start open.
  • Inside each card the Share permissions and NTFS permissions, each with account and rights; deny entries are marked Deny, and the four open principals are highlighted.

When the check can't run

If the query itself fails, the check reports an error instead of a status — none of these messages say anything about the shares.

MessageWhat to do
Query timed out after …s.Listing the shares and their permissions took longer than the query timeout. Raise Query timeout (seconds) under the advanced options.
Query returned no output.The query ended without a result. Usually temporary — worth a look at the device only if it repeats.
Query failed: …Windows reported an error while reading the shares; the message shows it verbatim.
Get-SmbShare is not available on this system (requires Windows 8/Server 2012 or newer).The Windows release is missing the SMB PowerShell module the check uses. Run the check on Windows 8, Windows Server 2012 or newer.
Any other message, shown on its own without a Query … prefix.The check stopped on an unexpected error and passes the message through unchanged. Worth a look at the device if it repeats.