Reduce Standing Privileges for Stronger Network Security | EnSight+

Within cybersecurity, “privileged accounts” and so-called standing privileges have been recent hot-button issues. By definition, a privileged user is one with administrative permissions to one or more systems. This is usually an administrator/”superuser” or someone who can perform maintenance on the network and make system-wide changes.

Related: With Cybersecurity Scrutiny Increasing, Software is the Best Line of Defense

The problem with privileged accounts is that many times, someone becomes multiple someones with teams of IT professionals sharing a single log-in for the sake of convenience and simplicity. For that reason and others, privileged accounts have become ripe targets for cybersecurity threats. In fact, some analysts have suggested that upwards of 80% of security breaches involve privileged accounts. Today, we delve deeper into this problem by talking through the concept of reducing standing privileges, and how EnSight+ can support that strategy.

Traditional Privileged Access Management (PAM) creates problems

Any company with a network infrastructure hosting critical data or assets (like sensitive customer or company information) has historically relied on privileged accounts and the use of a PAM structure. In theory, PAM makes sense. It utilizes passwords that are often complex in nature for data protection. Where PAM falls short is that it enables broad privileges, shared accounts, and third-party access. All leading to standing privileges.

Related: Shifting to Remote Work? Here’s How to Create a Secure Infrastructure

A closer look at standing privileges

Another way to describe standing privileges is “always on.” In other words, a user that has standing privileges will have consistent access to information and data at all times, regardless of what data they actually need for a given task. It’s easy to see how this can cause concern, especially in an organization that houses sensitive information like customer credit card details. Always-on permissions heighten cyber-vulnerabilities by offering more “doors” for hackers in search of that sensitive information to enter.

Related: The Intersection of Cybersecurity and the Utility Industry

Cybersecurity experts agree that it’s best to eliminate the use of standing privileges, a strategy known as a zero-trust framework. This approach involves the company restricting access controls to only what the user needs to complete their work.

Related: The Costs and Dangers of Data Breaches in Energy and Utilities

EnSight+ enables a zero-trust framework

As the provider of a field service software solution, EnSight+ understands the importance of specialized access. However, we also recognize that field service companies are often in possession of the type of data that fraudsters covet. The onus is on the company to take the proper precautions to keep that data safe. And that’s a big reason why so many field service companies have turned to EnSight+ for our safe and secure field service software solution.

Related: Data Security Through Software Vendors

EnSight+ allows companies to completely customize and control all access to secure data, supporting that recommended zero-trust framework. Leadership can assign specific permissions to office staff and field workers on an individual level. In addition, we prevent unauthorized access by blocking specific IP addresses. We can also add an additional layer of security by permitting sign-on via VPN only. Our data security teams can also work with you to identify network weaknesses and deliver regular threat assessments to ensure your team is always aware of any potential or looming threats.

To learn more about how EnSight+ can keep your network safe and help you reduce standing privileges, book your demo today.


Multiple field workers. Multiple tasks. Multiple vehicles. One simple piece of software

All monitored by you, in real time. Are you ready to take control?

  • We will never sell or distribute your personal information.
  • This field is for validation purposes and should be left unchanged.