Category: Windows Server/Client


Reference:

Need 2012 R2 Domain functional level on the forest to use authentication silos/policies

Their are part of the configuration partition (so, at the forest level), replicated on all domain controllers

 

https://github.com/MicrosoftDocs/windowsserverdocs/blob/master/WindowsServerDocs/security/credentials-protection-and-management/authentication-policies-and-authentication-policy-silos.md

 

https://docs.microsoft.com/en-us/windows-server/security/credentials-protection-and-management/authentication-policies-and-authentication-policy-silos#BKMK_HowKerbUsed

 

Videos:

Advertisements

There’s Something About Service Accounts

 

 

Full article:

https://401trg.com/an-introduction-to-smb-for-network-security-analysts/

 

Introduction:

At its most basic, SMB is a protocol to allow devices to perform a number of functions on each other over a (usually local) network. SMB has been around for so long and maintains so much backwards compatibility that it contains an almost absurd amount of vestigial functionality, but its modern core use is simpler than it seems. For the most part, today SMB is used to map network drives, send data to printers, read and write remote files, perform remote administration, and access services on remote machines.

SMB runs directly over TCP (port 445) or over NetBIOS (usually port 139, rarely port 137 or 138). To begin an SMB session, the two participants agree on a dialect, authentication is performed, and the initiator connects to a ‘tree.’ For most intents and purposes, the tree can be thought of as a network share.[1] The PCAP below, shown in Wireshark, demonstrates a simple session setup and tree connect. In this case, the machine 192.168.10.31 is connecting to the “c$” share (equivalent to the C:\ drive) on the 192.168.10.30 machine, which is called “admin-pc

 

When you connect to remote Server Message Block (SMB) services shares by using \\192.x.y.z\share name, Kerberos is not used, and the Internet Protocol (IP) SMB file share access does not use Kerberos. A network trace shows the following Kerberos error in the KRB_ERROR: Server not found in Kerberos database

Cause:

By default, Microsoft Windows Server 2003 and Microsoft Windows 2000 try to use Kerberos as the security provider. When a client uses Kerberos to authenticate itself to a server, the client requests a session ticket for the Service Principal Name (SPN). IP addresses are not names, so Kerberos is not used. After this occurs, the server goes through the list of the other supported security providers.

Status:

This behavior is by design.
IP addresses typically change, and it is not workable to add these addresses as SPNs. An SPN can be one of the following:

•The DNS name for the domain.
•The DNS name of a host.
•The distinguished name of a service connection point object.

 Create VM:

https://docs.microsoft.com/en-us/azure/virtual-machines/windows/

Manage VM:

https://docs.microsoft.com/en-us/azure/virtual-machines/windows/vm-usage

 

Run PowerShell scripts in your Windows VM with Run Command:

https://docs.microsoft.com/en-us/azure/virtual-machines/windows/run-command

Run Command uses the VM agent to run PowerShell scripts within an Azure Windows VM. These scripts can be used for general machine or application management and can be used to quickly diagnose and remediate VM access and network issues and get the VM back to a good state.

Overview:

https://docs.microsoft.com/en-us/powershell/dsc/overview/overview

https://docs.microsoft.com/en-us/powershell/dsc/resources/resources

Blog: https://blogs.msdn.microsoft.com/powershell/2018/09/13/desired-state-configuration-dsc-planning-update-september-2018/

DSC resource kit:

https://github.com/powershell/dscresources

Troubleshooting DSC:

https://docs.microsoft.com/en-us/azure/automation/troubleshoot/desired-state-configuration

DSCEA:

https://github.com/Microsoft/DSCEA

readme: https://microsoft.github.io/DSCEA/

 

Following commands to be added twice to Linux and Windows :

Linux:

net ads dns register -P

Windows:

ipconfig /registerdns

Attack surface analyzer:

https://www.microsoft.com/security/blog/2019/05/15/announcing-new-attack-surface-analyzer-2-0

 

DSC-EA:

https://github.com/Microsoft/DSCEA

documentation: https://microsoft.github.io/DSCEA/

 

Microsoft security compliance toolkit:

Il remplace Security Compliance Manager. Cet outil permet de planifier, créer, et monitorer des baselines de sécurité pour vos postes clients. Le remplacement a été choisi par Microsoft du fait de la complexité de SCM et de la difficulté à maintenir l’outil pour chaque version de Windows. Aujourd’hui, SCT ne supporte pas Desired Configuration Management de System Center Configuration Manager ou SCAP.

https://www.microsoft.com/en-us/download/details.aspx?id=55319

how to use it:

https://arnaudloos.com/2018/intro-to-policy-analyzer/

https://github.com/MicrosoftDocs/windows-itpro-docs/blob/master/windows/security/threat-protection/security-compliance-toolkit-10.md

 

Other references:

2012 R2 hardening (CIS):

https://www.cisecurity.org/wp-content/uploads/2017/04/CIS_Microsoft_Windows_Server_2012_R2_Benchmark_v2.2.0.pdf

Windows 10 hardening:

https://www.asd.gov.au/publications/protect/Hardening_Win10.pdf

 

 

 

Security baseline reference article:

https://blogs.technet.microsoft.com/secguide/2019/04/24/security-baseline-draft-for-windows-10-v1903-and-windows-server-v1903/

Introduction:

Download the content here: Windows-10-1903-Security-Baseline-DRAFT. As usual, the content includes GPO backups, GPO reports, scripts to apply settings to local GPO, Policy Analyzer rules files for each baseline and for the full set, and spreadsheets documenting all available GPOs and our recommended settings, settings that are new to this Feature Update, and changes from the previous baselines.

Note that Windows Server version 1903 is Server Core only and does not offer a Desktop Experience (a.k.a., “full”) server installation option. In the past we have published baselines only for “full” server releases – Windows Server 2016 and 2019. Beginning with this release we intend to publish baselines for Core-only Windows Server versions as well. However, we do not intend at this time to distinguish settings in the baseline that apply only to Desktop Experience. When applied to Server Core, those settings are inert for all intents and purposes.

This new Windows Feature Update brings very few new Group Policy settings, which we list in the accompanying documentation. The draft baseline recommends configuring only two of those. However, we have made several changes to existing settings, and are considering other changes. Please review the changes carefully and let us know what you think.

The changes from the Windows 10 v1809 and Windows Server 2019 baselines include:

  • Enabling the new “Enable svchost.exe mitigation options” policy, which enforces stricter security on Windows services hosted in svchost.exe, including that all binaries loaded by svchost.exe must be signed by Microsoft, and that dynamically-generated code is disallowed. Please pay special attention to this one as it might cause compatibility problems with third-party code that tries to use the svchost.exe hosting process, including third-party smart-card plugins.
  • Configuring the new App Privacy setting, “Let Windows apps activate with voice while the system is locked,” so that users cannot interact with applications using speech while the system is locked.
  • Disabling multicast name resolution (LLMNR) to mitigate server spoofing threats.
  • Restricting the NetBT NodeType to P-node, disallowing the use of broadcast to register or resolve names, also to mitigate server spoofing threats. We have added a setting to the custom “MS Security Guide” ADMX to enable managing this configuration setting through Group Policy.
  • Correcting an oversight in the Domain Controller baseline by adding recommended auditing settings for Kerberos authentication service.
  • Dropping the password-expiration policies that require periodic password changes. This change is discussed in further detail below.
  • Dropping the specific BitLocker drive encryption method and cipher strength settings. The baseline has been requiring the strongest available BitLocker encryption. We are removing that item for a few reasons. The default is 128-bit encryption, and our crypto experts tell us that there is no known danger of its being broken in the foreseeable future. On some hardware there can be noticeable performance degradation going from 128- to 256-bit. And finally, many devices such as those in the Microsoft Surface line turn on BitLocker by default and use the default algorithms. Converting those to use 256-bit requires first decrypting the volumes and then re-encrypting, which creates temporary security exposure as well as user impact.
  • Dropping the File Explorer “Turn off Data Execution Prevention for Explorer” and “Turn off heap termination on corruption” settings, as it turns out they merely enforce default behavior, as Raymond Chen describes here.

 

 

 

  • Microsoft Security Response Center: Protection, detection, and response.
  • Malware Protection Center: The Microsoft Malware Protection Center (MMPC) provides world class antimalware research and response capabilities that support Microsoft’s range of security products and services. With laboratories in multiple locations around the globe the MMPC is able to respond quickly and effectively to new malicious and potentially unwanted software threats wherever and whenever they arise.
  • My Bulletins: Is an online tool that provides you with a personalized list of the Microsoft security bulletins that matter most to you. Support for My Bulletins is being deprecated as Microsoft moves to simplify the update terminology and process. Going forward please use the Security Update Guide (SUG) for a more relevant and customizable way to track updates.
  • Security Update Guide (SUG): The Security Update Guide is the authoritative source of information on our security updates. It provides guidance, response, bulletin and advisory information and you can even get Security Update information through the API.
  • CSS YouTube Channel for customers: Now customers get a seamless self-service experience across our support sites and social channels. Check out the new CSS channel on YouTube – view it, like it, subscribe to it. The more activity, the easier it is for customers to find us when they need our help.
  • Blog MS Monthly: Blog MS consolidates a large number of highly relevant and up to date information sources across the Microsoft product and online services portfolio. You can expect to find important announcements and details of Microsoft news, product releases, service packs and important support issues.
  • Microsoft Premier Support: The Microsoft Premier Support (MPS) site is a secure Web site for the exclusive use of Premier Support customers. Note some of the links below may only be available to Premier Support customers. If you currently have Premier Support and don’t have access to MPS, please let your TAM know. Your TAM can get you access to the site.
  • Premier Services Twitter: Microsoft Premier Services is now on Twitter!  This account will share new proactive offerings and product information, links to important articles on TechNet or Microsoft Blogs, important lifecycle updates, and security alerts.  Start following us today!
  • otection, detection, and response.
  • Malware Protection Center: The Microsoft Malware Protection Center (MMPC) provides world class antimalware research and response capabilities that support Microsoft’s range of security products and services. With laboratories in multiple locations around the globe the MMPC is able to respond quickly and effectively to new malicious and potentially unwanted software threats wherever and whenever they arise.
  • My Bulletins: Is an online tool that provides you with a personalized list of the Microsoft security bulletins that matter most to you. Support for My Bulletins is being deprecated as Microsoft moves to simplify the update terminology and process. Going forward please use the Security Update Guide (SUG) for a more relevant and customizable way to track updates.
  • Security Update Guide (SUG): The Security Update Guide is the authoritative source of information on our security updates. It provides guidance, response, bulletin and advisory information and you can even get Security Update information through the API.
  • CSS YouTube Channel for customers: Now customers get a seamless self-service experience across our support sites and social channels. Check out the new CSS channel on YouTube – view it, like it, subscribe to it. The more activity, the easier it is for customers to find us when they need our help.
  • Blog MS Monthly: Blog MS consolidates a large number of highly relevant and up to date information sources across the Microsoft product and online services portfolio. You can expect to find important announcements and details of Microsoft news, product releases, service packs and important support issues.
  • Microsoft Premier Support: The Microsoft Premier Support (MPS) site is a secure Web site for the exclusive use of Premier Support customers. Note some of the links below may only be available to Premier Support customers. If you currently have Premier Support and don’t have access to MPS, please let your TAM know. Your TAM can get you access to the site.
  • Premier Services Twitter: Microsoft Premier Services is now on Twitter!  This account will share new proactive offerings and product information, links to important articles on TechNet or Microsoft Blogs, important lifecycle updates, and security alerts.  Start following us today!