Dark Reading is part of the Informa Tech Division of Informa PLC

This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them.Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.

Perimeter

12/17/2018
10:30 AM
Mark B. Cooper
Mark B. Cooper
Commentary
Connect Directly
Twitter
LinkedIn
RSS
E-Mail vvv
0%
100%

Shhhhh! The Secret to Secrets Management

Companies need to take a centralized approach to protecting confidential data and assets. Here are 12 ways to get a handle on the problem.

Organizations in all industries have secrets that need to be protected. The modern ID landscape is filled with secrets — passwords, encryption keys, cryptocurrency wallets, SQL connection strings, storage account keys, API tokens — and organizations are challenged with storing, managing, and protecting their secrets.

Let's define "secrets" as some knowledge or a piece of data that should be hidden from others, such as unapproved employees, unrelated business units, and competitors. Secrets are often used to encrypt data at rest and in transit. For example, a website will typically access encrypted data, process the information, and present the resulting information to a user in a browser. The data must be unencrypted for processing and transmission to the user.

If secrets aren't managed correctly, they can expose sensitive information that could wreak havoc on an organization, its network, and its data. Currently, 87% of executives lack confidence in their organization's level of cybersecurity, according to EY, a member firm of Ernst & Young Global Limited. Knowing where secrets are kept is the first step, which is easier said than done. They are likely fragmented and scattered everywhere across the organization and beyond: on premises, in the cloud, on servers, on devices, on clients, and even in code. A centralized approach to secrets management is vital for companies to protect their data and assets, while a poorly managed security approach could lead to breach, noncompliance, or outage.

12 Ways to Get a Handle on Secrets Management

  1. Learn where your company's secrets are kept and inventory them.  Secrets are often scattered everywhere: on premises; on servers, devices, and clients; in the cloud, and even in code. Develop a checklist to discover which systems are using keys, and collect information on their secret requirements and integration points.
  2. Set your goals for security robustness. The more robust your security, the more complex the implementation. You'll need to have guidelines and practices in place for your extended security team to include user access policies, automated systems updates, and secure code deployment.
  3. Centralize your approach. Place secrets in a private repository with restricted access. Leverage vaulting systems (such as password managers) with access management. Leverage systems such as PKI to utilize keys requiring lower management of keys.
  4. Separate data from the secrets. You can use location to your advantage and keep the secrets on premises and data in the cloud.
  5. Define your implementation. Evaluate administration versus technology solutions (see section below). Determine if you will use policy and custom processes or will leverage an existing vendor solution to achieve your goal
  6. Control access. Consider security around any centralized repository. Manage control of access, authorizations, permissions, and privileges.
  7. Remove the human factor, if possible. Limit employees' access to the secrets, leverage escrow services when passwords are involved, and consider alternate identity solutions in lieu of passwords.
  8. Check permissions: users, machines, applications. Determine where secrets are being created and stored and enforce restrictions that prevent unapproved creation and storage in unmanaged places.
  9. Log use and look for patterns. Anomaly detection will help you better understand and assess data and user behavior.
  10. Rotate encryption and identity keys. Define lifetimes and rotation strategies so encryption keys are removed from use before their cryptographic lifetimes are exceeded.  
  11. Have an incident response plan ready. With threats and errors occurring with increased regularity, an incident response plan will reduce your risks (and stress) if you are faced with a security incident, requiring urgent incident response.
  12. Plan ahead for data breach to reduce the impact. Having your breach response plan always updated will help if there is any type compromise.

Once secrets are located by performing an assessment and inventory, it's crucial to separate data from the secrets. For example, make sure the encryption keys that protect the data are separate from the secrets in a central, private repository with restricted access — such as a key management server with limited access to the public and by your employees. One recommendation is to use location to your advantage: secrets on-premises, data in the cloud. Be sure to keep data encrypted using keys and ensure keys are encrypted at rest.

Administration vs. Technology Solutions
The human element will always be the weakest link in any security protocol. Consider this: 80% of data breaches are caused by silly mistakes made by those responsible for managing secrets, according to Rashmi Jha, senior program manager at Microsoft. Here are some principles for tightening up your security:

  • Leverage escrow services when passwords are involved.
  • Consider alternate identity solutions in lieu of passwords.
  • Key management solutions are only part of the equation.
  • Audit, compliance, and remediation are critical.
  • Consider security around any centralized repository.

Levels of Security
Depending on your resources, there are different levels of security to consider when protecting your organization’s secrets:

  • Limited access: Secrets are stored in a repository/server with limited access to the public. Examples include password vaults, hardware security modules, and private Git repositories.
  • Encrypted secrets: Before being stored, the secrets are encrypted. Security through obscurity is not acceptable.
  • Management: An application that allows high-level control of the secrets. Examples include symmetric key management systems and password escrow services.

The Carrot or the Stick
Managing your organization's secrets is one thing, but what about the third parties that you work with on an ongoing basis? Will secrets management be defined by your vendor's application capabilities? If so, your vendors will be indirectly dictating your security posture. Application support is of utmost importance for the security of your secrets. You'll want to define your own secrets management goals, establish a baseline standard for today, and create a two- to five-year goal for your security standard. You will want to be in control and notify your vendors that they must support the standard or face replacement. Any new RFP and application selection process criteria will factor in new requirements before acquisition.

The Pitfalls of Poor Secrets Management
What happens if organizations have poor secrets management? It can lead to account and network compromise, information leaks, outages, compliance issues, data breach, loss of reputation — and even the business shutting down. Secrets management is an ongoing effort and it's important to follow the "trust but verify" approach.

Related Content:

 

Mark B. Cooper, President and Founder of PKI Solutions, has been known as "The PKI Guy" since his early days at Microsoft. Mark has deep knowledge and experience in all things public key infrastructure (PKI), including Microsoft Active Directory Certificate Services ... View Full Bio
Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
Why Cyber-Risk Is a C-Suite Issue
Marc Wilczek, Digital Strategist & CIO Advisor,  11/12/2019
Unreasonable Security Best Practices vs. Good Risk Management
Jack Freund, Director, Risk Science at RiskLens,  11/13/2019
6 Small-Business Password Managers
Curtis Franklin Jr., Senior Editor at Dark Reading,  11/8/2019
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Write a Caption, Win a Starbucks Card! Click Here
Latest Comment: This comment is waiting for review by our moderators.
Current Issue
Navigating the Deluge of Security Data
In this Tech Digest, Dark Reading shares the experiences of some top security practitioners as they navigate volumes of security data. We examine some examples of how enterprises can cull this data to find the clues they need.
Flash Poll
Rethinking Enterprise Data Defense
Rethinking Enterprise Data Defense
Frustrated with recurring intrusions and breaches, cybersecurity professionals are questioning some of the industrys conventional wisdom. Heres a look at what theyre thinking about.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2019-18980
PUBLISHED: 2019-11-14
On Signify Philips Taolight Smart Wi-Fi Wiz Connected LED Bulb 9290022656 devices, an unprotected API lets remote users control the bulb's operation. Anyone can turn the bulb on or off, or change its color or brightness remotely. There is no authentication or encryption to use the control API. The o...
CVE-2019-17391
PUBLISHED: 2019-11-14
An issue was discovered in the Espressif ESP32 mask ROM code 2016-06-08 0 through 2. Lack of anti-glitch mitigations in the first stage bootloader of the ESP32 chip allows an attacker (with physical access to the device) to read the contents of read-protected eFuses, such as flash encryption and sec...
CVE-2019-18651
PUBLISHED: 2019-11-14
A cross-site request forgery (CSRF) vulnerability in 3xLogic Infinias Access Control through 6.6.9586.0 allows remote attackers to execute malicious and unauthorized actions (e.g., delete application users) by sending a crafted HTML document to a user that the website trusts. The user needs to have ...
CVE-2019-18978
PUBLISHED: 2019-11-14
An issue was discovered in the rack-cors (aka Rack CORS Middleware) gem before 1.0.4 for Ruby. It allows ../ directory traversal to access private resources because resource matching does not ensure that pathnames are in a canonical format.
CVE-2019-14678
PUBLISHED: 2019-11-14
SAS XML Mapper 9.45 has an XML External Entity (XXE) vulnerability that can be leveraged by malicious attackers in multiple ways. Examples are Local File Reading, Out Of Band File Exfiltration, Server Side Request Forgery, and/or Potential Denial of Service attacks. This vulnerability also affects t...