The Risks To You And Your Organisation Of Not Using An SSH Key Manager For Your User Keys

Organisations large and small may have multiple servers and maybe tens of thousands of data users who have access to one of their company’s most valuable assets – their data. Typically data users – not even necessarily the human kind – are issued with authentication keys and a pair is produced – a public/private pair for authentication and supposed safe access to the information but there are serious risks which mean that the management of those keys is vital to make sure the information doesn’t fall into the wrong hands. Here are the main risks that can be addressed by the new SSH Key Manager. createssh

Unauthorised Copies of Private Keys. directory24x7

Any administrator who has access to a user account is technically able to make a copy of any private key stored in that account.This could be any user who can thereafter log into the client account and may have made a copy. Such copies are just as effective for public key authentication as the original keys as long as the public keys remain authorised by the servers. supermoz

Lack of Key Rotation.

Changing keys is currently too costly and difficult in practice. As a result, many of the private keys in the environment could be years old and any numbers of parties such as administrators, contractors, employees and consultants could still have access and it would be impossible to track them down. buddylinks

Lack of Visibility of Who has Access to What.

Typically most organisations don’t know which users have access to which servers and data. Automated data transfer means that data could easily be flowing to users who shouldn’t have access to it. It’s important to know that who has access to what sort of data and to manage those security levels. seoboost

Lack of Visibility of Trust Relationships Cross Production or Functional Boundaries.

Many organisations have policies stating that file transfers or application to application connections should not occur between their production networks and development networks. Firewalls can be used to help with this but they do not have visibility of the user accounts used within encrypted sessions, so cannot see inside the encryption so there is no visibility of whether there are trust relationships crossing the boundary.

Lack of Visibility of Trust Relationships Crossing Organisational Boundaries.

Many organisations outsource some or all of their IT to external providers. Often those providers administer the servers and thus have access to the network from its premises. Such access is usually implemented using the SSH protocol. Many of these organisations cannot see whether the trust relationships for passwordless authentication exist between their provider and themselves. This can expose the organisation to rogue service provider’s personnel and even systematic data leaks.

Inability to Audit Existing Trust Relationships.

Lack of visibility of existing user authentication keys also means that it is not possible to audit them. For most, it’s not possible to audit the following:

Regular renewals of private keys, nil-use of private key, length of use of private key, who has access to what data, which servers, hosts or applications, who can create new accounts and the level of trust relationship, ex employees or contractors who might be accessing the system, adjustment of account access dependent on their role or seniority, unauthorised data transfer.

The Quantity of Individuals Who Can Create Permanent Trust Relationships.

When trust relationships are set up manually by individual administrators, there’s no control over what trust relationships are set up and whether they are properly documented and approved. Large enterprises might have a very large number of people and the more people there are and trust relationships. The higher the number there is, the greater the risk.

Human Errors in Manual Key Set up and Removal Process.

The process of setting up a password-less trust relationship involves creating a key pair by copying the generated key.



Related Posts

Leave a Reply

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