# NetBIOS name standard compliance should be retrievable

NetBIOS names are still used in many Windows networking scenarios, even though DNS is the primary name resolution method.

Source: https://maester.dev/docs/tests/AD-DOM-07

<!-- This file is generated by website/scripts/generate-test-docs.mjs. Do not edit manually. -->

<div class="test-byline"><div class="test-byline-avatars"><a class="test-byline-avatar test-byline-avatar--author" href="/contributors/soulemike" title="Michael Soule · Original author"><img src="https://github.com/soulemike.png" alt="Michael Soule" width="28" height="28" loading="lazy" decoding="async" /></a></div><div class="test-byline-meta"><span class="test-byline-text">Contributed by <a href="/contributors/soulemike">Michael Soule</a></span><a class="test-byline-link" href="/contributors">All contributors →</a></div></div>

<p class="test-part">Part of <a href="/docs/tests/ad">Active Directory</a> · Active Directory · Domain and forest · <a href="/docs/tests">All checks</a></p>

```powershell title="Run this check"
Invoke-Maester -TestId AD-DOM-07
```

## Overview

NetBIOS names are still used in many Windows networking scenarios, even though DNS is the primary name resolution method. Non-compliant NetBIOS names can cause:

- **Legacy Application Issues**: Older applications may not handle non-standard characters
- **WINS Problems**: Windows Internet Name Service may have trouble with invalid names
- **Network Browsing**: Issues with network neighborhood and browsing services
- **Script Failures**: PowerShell and batch scripts may fail with special characters

Valid NetBIOS names should:
- Be 1-15 characters in length
- Contain only alphanumeric characters and: !@#$%^&'()_-.+{}~
- Not contain: \ / : * ? " < > |

#### Control Type

**Preventive**

#### Security Recommendation

- **Use Simple Names**: Stick to alphanumeric characters for maximum compatibility
- **Keep Short**: Stay well under the 15-character limit
- **Avoid Special Characters**: Even allowed special characters can cause issues
- **Document Requirements**: If special characters are needed, document the business case

#### How the Test Works

This test validates NetBIOS names against standard naming conventions, checking for valid characters and length requirements.

#### Related Tests

- `Test-MtAdNetbiosNameNonStandardDetails` - Lists non-compliant NetBIOS names
- `Test-MtAdDomainNameStandardCompliance` - Checks domain name compliance

## Details

<details>
<summary>Every attribute of this check</summary>

| Field | Value |
| --- | --- |
| Test ID | AD-DOM-07 |
| Severity | Info |
| Suite | Active Directory |
| Product | Active Directory |
| Feature | Domain and forest |
| Area | Infrastructure hardening |
| Resource type | Tenant |
| MITRE ATT&CK | None |
| PowerShell test | [Test-MtAdNetbiosNameStandardCompliance](https://github.com/maester365/maester/blob/main/tests/ad/domain/Test.AD-DOM-07.ps1) |
| Services | ActiveDirectory |
| Permissions | ActiveDirectory:Ldap:domainDNS:ReadProperty |

</details>

## Source

- Test: [`tests/ad/domain/Test.AD-DOM-07.ps1`](https://github.com/maester365/maester/blob/main/tests/ad/domain/Test.AD-DOM-07.ps1)
- Documentation: [`tests/ad/domain/Test.AD-DOM-07.md`](https://github.com/maester365/maester/blob/main/tests/ad/domain/Test.AD-DOM-07.md)