Urgent.News

What's breaking now, across thousands of outlets.

Tech

Privileged access management skipped everyone between 50 and 500 engineers

Disclosure: I work on Tessera, which is one of the tools in the gap I am describing. Ask a fifty-person engineering organisation how they control production access and you will hear the same answer with small variations: a bastion host, SSH keys distributed by configuration management, a shared kubeconfig somewhere, and a spreadsheet or a Notion page that is out of date. Nobody chose that. It is…

In the middle ground between 50 and 500 engineers, privileged access management (PAM) tools have become unaffordable and ineffective. Traditional PAM solutions, designed for large enterprises with thousands of administrators and regulated industries, are priced per protected resource, which leads to escalating costs for growing teams. The realistic option for these mid-sized organisations is to build their own PAM solution, but this is often unrealistic due to the time and resources required.

Three recent shifts have enabled a viable alternative: self-hosting has become a feasible option, deployment no longer necessitates professional services, and pricing models have transitioned to per-seat pricing. As a result, organisations within this size bracket are now considering PAM tools that offer session-level control, audit evidence, and are priced accordingly.

Tessera, a self-hosted access broker for SSH, Kubernetes, databases, and RDP, is one such solution. With a free tier available for a single administrator, Tessera aligns with the pricing model that fits these organisations. Other similar tools include Teleport and Boundary, both of which have free tiers and can be deployed quickly without requiring any changes to your targets or additional installations on your infrastructure.

These tools can provide the necessary session-level control and audit evidence required to satisfy auditors and customers without incurring prohibitive costs. Therefore, it is recommended to implement such a solution before an audit to ensure evidence covers the audit period.

Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.

Read the original at dev.to →

More in Tech

Auditors do not want your policy. They want an artefact.

Disclosure: I work on an access tool (Tessera), mentioned once at the end. Everything before that is about evidence, and applies whatever you use.

  • Audits fail due to lack of evidence, not missing controls
  • Organizations need specific artifacts to satisfy auditors
  • Artifact properties: separate storage, immutability, exportability

Your access tool is a vendor with a copy of your infrastructure map

Disclosure: I work on Tessera, which is self-hosted. That is the position I am arguing from, and the costs of that position are in the last section.

  • Access tool is a vendor with infrastructure map copy
  • Security questionnaires overlook access-control role
  • Hosted access broker knows infrastructure details

What running your own SSH certificate authority actually costs

Disclosure: I work on Tessera, which is on the buy side of this. I have tried to cost the build side properly, because a comparison where the build option looks stupid is a comparison nobody believes.

  • Initial build takes about a week, including key generation and configuration.
  • Securing CA key adds 2-4 weeks of operational work due to HSM/KMS integration.
  • Ongoing maintenance costs around $15k–$50k annually, totaling $75k–$150k for build and upkeep.

More from Tuesday 1 September →