How to Harden Your

Enterprise in Today’s
Threat Landscape
Andrew Idell
Frank Brinkmann

February 1, 2017
Frank Brinkmann
• 19 years with Microsoft and more than 23 years in IT:
• Director, Cybersecurity Protection Team (CPT), part of the
Enterprise Cybersecurity Group. This team develops,
pilots, and maintains the cybersecurity consulting
offerings that protect our customers’ critical assets
Andrew Idell
• 13 years at Microsoft, 21 years total in IT
• Cybersecurity Architect – Cybersecurity Protection Team
(CPT), part of the Enterprise Cybersecurity Group
• Holds the CISSP and MCM: Directory Services
certifications
• Andrew’s career focused has on Active Directory, PKI, and
Windows Security, including work in Corporate IT, as an
Microsoft Certified Trainer, and as a consultant at
Microsoft Partners. Since joining Microsoft, Andrew has
spent time in Product Support, Microsoft Consulting
Services in Infrastructure and Cybersecurity, before
joining ECG at its beginning in 2015.
Agenda

The Security Challenge

Common Security Misconceptions

Addressing the Real Concerns

Conclusion and Take-Aways

1. The Security Challenge
Why is securing today’s datacenter a challenge?
These challenges can leave your business vulnerable
For example: The typical attack timeline & observations

24-48 Hours Average 140+ days 

Initial user Core security Service outage Attack

compromise compromised or data detected
or entry (Domain Admin) exfiltration
vector
2. Common Security
Misconceptions
“My enterprise needs to be very concerned
about 0-days.”
Actually...
Not overall, because most companies are compromised by old and unpatched
vulnerabilities in software running on top of Windows

https://www.microsoft.com/security/sir/default.aspx

http://www.infoworld.com/article/3075830/security/zero-days-arent-the-problem-patches-are.html
So what should I do?
Step 1:

Step 2:

Step 3:
 How can Microsoft help me?
Option 1:

VULNERABILITY AND
PATCH MANAGEMENT

Option 2:

MALWARE
DETECTION

Option 3:

SECURITY INVESTIGATION
AND EVENT MONITORING
“Will using systems management and security software on
my Domain Controllers improve my security?”
Not really…
If the agents are running as System or Administrator, and the administrators of
these systems are not properly protected

Why?

How?

• The Credential Tier Model

• Credential Hygiene
The Credential Tier Model
Rule #1:
Tier 0
Domain &
Enterprise
Admins
Rule #2:

Tier 1
Rule #3:
Server
Admins

Tier 2
Workstation
& Device
Admins
When those rules aren’t followed: a typical attack chain

24-48 Hours Tier 0

Domain &
1. Beachhead (Phishing Attack, etc.) Enterprise
Admins
2. Lateral Movement
a. Steal Credentials
b. Compromise more hosts &
credentials
3. Privilege Escalation Tier 1
a. Get Domain Admin credentials Server
4. Execute Attacker Mission Admins
a. Steal data, destroy systems, etc.
b. Persist Presence

Tier 2
Workstation
& Device
Admins
So what should I do?
Step 1:

Step 2:

Step 3:
How can Microsoft help me?
Option 1:
http://aka.ms/cyberpaw

http://aka.ms/tiermodel

Option 2:
“Using jump servers and multi-factor
authentication protect my administrators”
Not really…
If the system used to log in with multi-factor authentication to your jump
servers is compromised.

Why?

Don’t new OS features like Credential Guard, Device Guard and Defender ATP mitigate
these threats?

And what about multi-factor authentication like Smart Cards and Windows Hello for Business?
Why the starting point has to be clean:
So what should I do?
Step 1:

Step 2:

Step 3:
How can Microsoft help me?
Option 1:
http://aka.ms/cyberpaw

http://aka.ms/cleansource

Option 2:
“Using virtualization and shared infrastructure in my Private
Cloud reduces complexity, thereby increasing security”
Not really…
Unless the virtual machines can be isolated from the virtualization admins, and
their storage encrypted with a key inaccessible by any storage administrators.
Why?

What is the issue?

Why are Domain Controllers special?

So what should I do?

Option 1:

Option 2:
How can Microsoft help me?
Option 1:

https://blogs.technet.microsoft.com/datacentersecurity/2016/03
/16/windows-server-2016-and-host-guardian-service-for-
shielded-vms/

Option 2:
3. Addressing the Real
Concerns
Every misconception is based on a legitimate concern
Security Need or Concern Solutions Microsoft Services Offerings

Protecting Administrators and their • Use hardened, dedicated workstations for • Privileged Access Workstation (PAW)
Credentials administrative tasks • Enhanced SecurityAdministrative
• Deploy a separate, hardened forest for Environment (ESAE)
your admin users and workstations
Hardening Tier-0 Servers • Remove upstream risks • Active Directory Hardening (ADH)
• Deploy Shielded VMs and the Host • HGS for Guarded Fabric and Shielded VMs
Guardian Service • Offline Assessment for
• Deploying official Windows Security Active Directory Services (OAADS)
Templates to DCs and other Tier
- 0 servers
Hardening Active Directory • Reducing membership in Tier- 0 groups • Active Directory Hardening (ADH)
• Deploying official Windows Security • Offline Assessment for
Templates Active Directory Services (OAADS)
• Implementing an OU and policy structure
that enforces the Tier Model
Detecting and Responding to Attacks • Deploying a detection solution that • Enterprise Threat Detection (ETD)
leverages machine learning to reduce the • Advanced Threat Analytics
“noise” and false positives Implementation Services (ATA-IS)
• Operations ManagementSuite, Advanced
Threat Analytics or Windows Defender ATP
4. Conclusion/Take-Aways
Key Take-Aways

Common security misconceptions are Microsoft has public guidance for Microsoft Services can help
a reflection of genuine security solutions to address these concerns. accelerate the adoption of these
concerns. solutions in your enterprise.
Reference Links
Privileged Access Workstation: http://aka.ms/cyberpaw

The Credential Tier Model: http://aka.ms/tiermodel

The clean-source principle: http://aka.ms/cleansource

The Ten Immutable Laws of Security Administration:

https://technet.microsoft.com/en-us/library/cc722488.aspx

Sticking with Well-Known and Proven Solutions:

https://blogs.technet.microsoft.com/fdcc/2010/10/06/sticking-with-well-known-and-
proven-solutions/

Responding to IT Security Incidents:

https://technet.microsoft.com/en-us/library/cc700825.aspx
© 2016 Microsoft Corporation. All rights reserved. The text in this document is available under the Creative Commons Attribution 3.0 License, additional terms may apply. All other content contained in this
document (including, without limitation, trademarks, logos, images, etc.) are not included within the Creative Commons license grant. This document does not provide you with any legal rights to any
intellectual property in any Microsoft product. You may copy and use this document for your internal, reference purposes.
This document is provided "as-is." Information and views expressed in this document, including URL and other Internet Web site references, may change without notice. You bear the risk of using it. Some
examples are for illustration only and are fictitious. No real association is intended or inferred. Microsoft makes no warranties, express or implied, with respect to the information provided here.