Yeah I don&#x27;t think a lot of people understand the lengths some companies go to, to control access to their systems (either because of risk aversion, regulatory requirements, or something else). It&#x27;s on a different planet from a startup mentality of &#x27;We hire trustworthy people, so all 10 employees have access to prod&#x27;. This is &#x27;How do we protect customer data from 1 in 2000 IT staff across 100 countries?&#x27;<p>For example, I was working at a massive bank that was implementing an access control system for their servers that meant that admin&#x27;s didn&#x27;t have direct access. You had to<p>- submit a change ticket that went through all the approvals.<p>- This triggered a workflow through a web interface that opened an RDP or text terminal session to the server, for the appropriate person (OS, application, database, etc)<p>- The RDP session was recorded to video, the text session was logged.<p>- Once you logged out the password on the server was auto-rotated.<p>- The text-session was indexed and searchable. The software coordinating all this was able to match server logs against the <i>video RDP session</i> so you could search through the video (&quot;show me the SQL Server commands that admin ran&quot;)<p>- On a regular basis, the server state would be reconciled against all the logged tickets for that server and discrepancies investigated.