Best Practice: Securing Windows Service Accounts and Privileged Access – Part 2

Voiced by Amazon Polly

In the first post I covered best practices for securing service accounts.  In this post, I am going to discuss some key elements in securing privileged access.  Keep in mind, Microsoft has published a comprehensive guide to securing an Active Directory.

Keep in mind that many of these things will require additional work on the front end, but that is usually due to poor existing practices.  Once processes are in place, these key components should not add significant overhead to administrative tasks.

    1. No users should regularly reside in Domain Admins (DA) or Enterprise Admins (EA) groups
    2. Straight from the horse’s mouth: As is the case with the Enterprise Admins (EA) group, membership in the Domain Admins (DA) group should be required only in build or disaster recovery scenarios. There should be no day-to-day user accounts in the DA group with the exception of the built-in Administrator account for the domain, if it has been secured as described in Appendix D: Securing Built-In Administrator Accounts in Active Directory.
    3. Follow MS’ recommendations for securing DA and EA accounts.
    4. If you are a single forest, single domain then no one needs to be in the enterprise admins period
    5. Configure tiered accounts for administrative access.  Reference (Updated 1/10/18)
    6. Ensure that priv accounts follow at least the standard password policy
    7. Don’t forget other privileged groups besides DA and EA (Schema Admins, Account Operators, Backup Operators, Administrators, etc.)
    8. Maintain separate admin credentials and standard user accounts
      1. Do not use the same account for admin access and for regular access
      2. This includes things like browsing the web on member servers or workstations with priv accounts
        1. Block internet access from all servers
      3. No remote access with privileged accounts
    9. Use a jump off server for admin tasks.
      1. Remote to it with a standard account and then remote from there to perform admin tasks
      2. You should allow interactive logons by authorized users and should remove or even block other logon types that are not needed for server access. (
      3. Admin functions should require more than one factor of authentication
      4. Or utilize privileged access workstations
    10. Use LAPS to generate a different password for all local admins
    11. Either use read only domain controllers in a DMZ or create a separate domain with a one way trust (trade off of complexity and security)
    12. Disable Macros for end users who do not have a need to run them.  Enable Trusted Locations for those that do.

[socialwrap align=”left”] [socialicon name=”fb” url=”” ][/socialicon] [socialicon name=”linkedin” url=”” ][/socialicon] [socialicon name=”twitter” url=”” ][/socialicon] [socialicon name=”google” url=”” ][/socialicon] [socialicon name=”rss” url=”” ][/socialicon] [socialicon name=”youtube” url=”” ][/socialicon] [socialicon name=”vimeo” url=”” ][/socialicon] [socialicon name=”pinterest” url=”” ][/socialicon] [socialicon name=”soundcloud” url=”” ][/socialicon] [socialicon name=”instagram” url=”” ][/socialicon] [socialicon name=”flickr” url=”” ][/socialicon] [socialicon name=”email” url=”” ][/socialicon] [/socialwrap]

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.