Machine learning means Smarter Cybersecurity™ Solutions.
As technology continues to advance, managing and analyzing massive data sets just can’t be accomplished by humans alone. It requires huge amounts of memory and storage, as well as high-speed processing of the cloud.
Course Of The Month
5 days, left to enrollBecome a Premium Member and unlock a new, free course in leading technologies each month.
Solved
MS15-011 - UNC hardening clarification?
Posted on 2016-08-10
Hello I am looking into better securing my Windows domain environment by following the steps per MS15-011 (KB3000483), where you use UNC hardening in Group Policy to specify the UNC paths domain workstations can connect to.
I'm a bit confused -- are you only suppose to add UNC paths to your domain controllers?
Or does this mean you're supposed to add any potential UNC path for any server, that any potential domain workstation or server could possible connect to (like a file share or anything else)?
Or is this only UNC path for Workstations pointing to Domain controller for group policy retrieval?
https://support.microsoft.com/en-us/kb/3000483
I'm a bit confused -- are you only suppose to add UNC paths to your domain controllers?
Or does this mean you're supposed to add any potential UNC path for any server, that any potential domain workstation or server could possible connect to (like a file share or anything else)?
Or is this only UNC path for Workstations pointing to Domain controller for group policy retrieval?
https://support.microsoft.com/en-us/kb/3000483
[X]
Welcome to Experts Exchange
Add your voice to the tech community where 5M+ people just like you are talking about what matters.
- Help others & share knowledge
- Earn cash & points
- Learn & ask questions
2
4 Comments
Active today
Recommended at minimum sysvol and netlogon shares
if you use \\server\* it will apply to all shares on that server \\*\sharename will apply to all shares with that sharename in the domain.
We recommend that all NETLOGON and SYSVOL shares be configured to require both mutual authentication and integrity in order to help secure Group Policy against spoofing and tampering attacks that can be leveraged to achieve remote code execution.
Hardened UNC paths
Value name Value
\\*\NETLOGON RequireMutualAuthentication=1, RequireIntegrity=1
\\*\SYSVOL RequireMutualAuthentication=1, RequireIntegrity=1
if you use \\server\* it will apply to all shares on that server \\*\sharename will apply to all shares with that sharename in the domain.
Active today
I guess I'm just wondering if I also need to manually add in an entry for file shares.
Like \\file01.domain.com\share1
Or the SCCM server for software deployments, or WSUS.
Or does this GPO not apply to UNC paths users may be accessing from their computer for things like that?
Only GPO's for computers?
Like \\file01.domain.com\share1
Or the SCCM server for software deployments, or WSUS.
Or does this GPO not apply to UNC paths users may be accessing from their computer for things like that?
Only GPO's for computers?
Active today
if it is not specified it doesn't apply
if you want to protect
\\file01.domain.com\share1
\\file01.domain.com\share2
\\file01.domain.com\share3
use the setting \\file01.domain.com\* and the settings you want this will be the default for that server
if you want to protect
\\file01.domain.com\share1
\\file01.domain.com\share2
\\file01.domain.com\share3
use the setting \\file01.domain.com\* and the settings you want this will be the default for that server
Active today
Recommended to do it anywhere, but definitely recommended for domain controller shares as mentioned.
But the most important thing is found here:
But the most important thing is found here:
Note: SMB Encryption is supported by the SMB client only on Windows 8, Windows Server 2012, and later versions, and then only when communicating with SMB Encryption-capable servers (such as Windows 8, Windows Server 2012 and later versions). If you configure RequirePrivacy=1 on clients that do not support SMB Encryption or for UNC paths hosted by servers that do not support SMB Encryption, you will have a configuration in which the SMB client will be unable to access the specified path.That simply means, if you have server 2008/2008R2 as server (or win7 or lower as client) and you try to set RequirePrivacy=1, then those shares are no longer accessible! The other two can be set, but if on 2008 (or, at the client side on xp/vista/7), avoid RequirePrivacy=1.
Featured Post
Question has a verified solution.
If you are experiencing a similar issue, please ask a related question
I was prompted to write this article after the recent World-Wide Ransomware outbreak. For years now, System Administrators around the world have used the excuse of "Waiting a Bit" before applying Security Patch Updates. This type of reasoning to me …
A 2007 NCSA Cyber Security survey revealed that a mere 4% of the population has a full understanding of firewalls. As business owner, you should be part of that 4% that has a full understanding.
- Superb Internet
- Hardware Firewalls
- Security
- Server Hardware
- Server Software
- *firewall management, *firewalls
This video Micro Tutorial shows how to password-protect PDF files with free software. Many software products can do this, such as Adobe Acrobat (but not Adobe Reader), Nuance PaperPort, and Nuance Power PDF, but they are not free products. This vide…
- Document Management
- Printers and Scanners
- Document Imaging
- Software-Other
- Images and Photos
- Adobe Acrobat, Photos / Graphics Software, Security, OCR, *PDF
There are cases when e.g. an IT administrator wants to have full access and view into selected mailboxes on Exchange server, directly from his own email account in Outlook or Outlook Web Access. This proves useful when for example administrator want…
Suggested Courses
Course of the Month5 days, left to enroll
688 members asked questions and received personalized solutions in the past 7 days.
Join the community of 500,000 technology professionals and ask your questions.