Alert icon Keyboard navigation enabled.
Alert icon TAB or Shift+TAB to navigate across. Down ↓ to open menu. ESC to close menu.
Alert icon Down ↓ to select section. Right → to activate. Up ↑ / Down ↓ / Tab to traverse all. ESC to exit.
BeyondTrust
Skip to content Use space or enter to skip.

What can we help you find today?

Instant Results
  • Website Results
  • Technical Documentation

Filter Options

Focus your search

Filtering by

Your recent searches:

Contact Us Chat with Sales Get Support
  • English
  • Deutsch
  • français
  • español
  • 한국어
  • português
  • Home
  • Resources
  • Blog
  • The Executive Order on Cybersecurity: Breaking it Down current page
Link copied

The Executive Order on Cybersecurity: Breaking it Down

Jul 31, 2017
Author:
Don Maclean
Chief Cybersecurity Technologist, DLT Solutions
Blog banner default
The Executive Order on Cybersecurity: Breaking it Down
Don Maclean
Chief Cybersecurity Technologist, DLT Solutions

Executive Order Cybersecurity

On May 11, 2017, the White House issued the catchily-titled "Presidential Executive Order on Strengthening the Cybersecurity of Federal Networks and Critical Infrastructure”, otherwise known as "The EO". The order is a broad and comprehensive document, imposing numerous requirements and policy changes throughout the Federal government. We can divide the document into four main categories, or work streams: accountability, modernization, vulnerabilities, and transparency. Let's take a look.

Check out my on-demand webinar "Addressing Executive Order on Cybersecurity Requirements to Mitigate Risk". View now

Accountability is primarily the mandate that agency heads be responsible for the security of their systems and data. It's a broad mandate ripe for further definition. More concretely, it requires a report from every agency on the risk posture of their systems, including a justification of all accepted risks. It also mandates identity and access management and privilege management, and requires the use of the Cybersecurity Framework (not to be confused with the NIST Risk Management Framework) for managing security and risk in Federal IT systems.

No matter the framework, assessing risk and justifying risk acceptance require thorough knowledge of a system and its vulnerabilities. To be accountable, it's also necessary to know who has access to a system, what they can do, and what they actually have done. Compliance with the EO will be much easier for agencies with the relevant tools.

The EO also urges modernization, not as a one-time effort, but as an ongoing business practice. It's essential to stay current, but ongoing modernization will require changes to procurement cycles and other long-standing government practices. Great idea, but will it happen? It's too soon to tell.

The EO also includes some very specific mandates about vulnerabilities. Sensibly, it requires repair of known vulnerabilities, with a focus on patch and configuration management. This goal is quite realistic, and could lead to a more solid security posture for our nation. It also requires the appropriate tool set.

Finally, transparency. The EO asks agencies to be more open about sharing, including best practices, and vulnerabilities they have found and fixed. Achieving this goal requires a difficult culture shift, but would move us toward a stronger security posture.

Compliance with the broader elements of the EO will require some unlikely culture shifts. The more specific mandates, however, are quite achievable for organizations with the relevant tools at hand.

To explore these work streams further and learn more about how BeyondTrust solutions can address the requirements of the EO check out this on-demand webinar. Or contact us to take a deeper dive into the unique needs of your agency.

Latest Posts
  • Hooked on Identity (Part 2): Abusing OAuth Trust Boundaries in Okta
    Jun 12, 2026 Hooked on Identity (Part 2): Abusing OAuth Trust Boundaries in Okta
    Blog
    7m
  • Hooked on Identity: Abusing SAML Assertion Inline Hooks in Okta
    Jun 9, 2026 Hooked on Identity: Abusing SAML Assertion Inline Hooks in Okta
    Blog
    6m
  • Joining Project Glasswing: Securing the Privilege Backbone of the AI Era
    Jun 8, 2026 Joining Project Glasswing: Securing the Privilege Backbone of the AI Era
    Blog
    5m
  • The Most Common & Most Dangerous Types of Shadow IT
    Jun 5, 2026 The Most Common & Most Dangerous Types of Shadow IT
    Blog
    19m
  • 14 Password Management Best Practices
    May 28, 2026 14 Password Management Best Practices
    Blog
    12m
Related
  • Learn what EMOTET is & How to Protect Against “The World’s Most Dangerous Malware”
    Aug 4, 2021 Learn what EMOTET is & How to Protect Against “The World’s Most Dangerous Malware”
    Blog
    1m
  • Do You Sudo? SHOULD You Sudo?
    Mar 14, 2011 Do You Sudo? SHOULD You Sudo?
    Blog
    1m
Share this Article
  • Link
Stay up to Date
Get the latest news, ideas, and tactics from BeyondTrust. You may unsubscribe at any time.

Keep up with BeyondTrust

Customer Support Get Started
  • LinkedIn
  • X
  • Facebook
  • Instagram
  • Add BeyondTrust as a preferred source on Google
  • Privacy
  • Security
  • Manage Cookies
  • Do Not Sell My Data
  • WEEE Compliance

Copyright © 2003 — 2026 BeyondTrust Corporation. All rights reserved. Other trademarks identified on this page are owned by their respective owners. BeyondTrust Corporation is not a chartered bank or trust company, or depository institution. It is not authorized to accept deposits or trust accounts and is not licensed or regulated by any state or federal banking authority.

Prefers reduced motion setting detected. Animations will now be reduced as a result.