Download the Checklist
Let’s talk about the unsung heroes of your on-premises infrastructure: network devices. These are the routers, switches, and firewalls that everyone forgets about…and takes for granted—until something breaks. And when one of those somethings breaks, it leads to some pretty bad stuff. If your network goes down, that’s bad, bad, bad for business. But if those devices lack the necessary security, well, that can leave you exposed in an incredibly dangerous way.
StrongDM manages and audits access to infrastructure.
- Role-based, attribute-based, & just-in-time access to infrastructure
- Connect any person or service to any infrastructure, anywhere
- Logging like you've never seen
Offboarding technical employees can be a complex and arduous process with a lot of moving parts. The key to successful offboarding is to have a clear understanding of what needs to be done, who does it, and how to monitor for any shenanigans from former employees.
That’s why we’ve pulled together the 2022 Tech Staff Offboarding Checklist. It outlines the steps you should take to make sure offboarding is done successfully.
BONUS: Below, we also breakdown how companies like MakeSpace, Hearst, and Fair use this process to improve security, protect sensitive data, and ensure a clean break with outgoing staff.
Why Do I Need an IT Offboarding Checklist?
“We are besieged by simple problems. ... Checklists can provide protection.”
― Atul Gawande, The Checklist Manifesto: How to Get Things Right
Offboarding technical employees typically requires working with IT and HR to revoke access to multiple systems, recover equipment, and help former employees exit on good terms. A well-structured checklist will help you:
- Protect your data.
- Mitigate legal and security threats.
- Uphold compliance standards.
- Ease the transition for remaining staff.
- Part on good terms.
Most of all, a checklist will give you assurance that you have dealt with every requirement of employee offboarding. If you don’t deal with them all, the risk for problems down the line can increase.
⚠️ Traditional PAM deployments have gaps. Learn how to protect your databases, the cloud, Kubernetes, and more with our legacy PAM augmentation guide.
Zombie Credentials and Bad Actor Threats
If your offboarding process doesn’t give you confidence that former staff no longer have access to your organization’s infrastructure, then chances are your environment is sprinkled with security gaps. That means former employees may still be able to delete files, misconfigure servers, alter data, or steal intellectual property. Not to mention that bad actors may discover forgotten keys, certificates, and “zombie credentials.”
Removing access is especially important for IT and security staff. These users often have far-reaching rights to shared folders, user email accounts, and other critical information. Users with network-wide access can even make significant changes in the environment.
To act quickly, you must maintain an accurate IT inventory, including knowledge of who has access to what and where—keys, credentials, certificates, etc.—and take care to revoke access from all sensitive systems. That’s why you can’t rely on severed SSO or VPN access alone. To prevent security breaches, you need a systematic way to revoke employee access across the board and an audit trail to ensure that your process is thorough and effective.
Simplifying the Offboarding Process
Failure to follow a plan can lead to more than just mistakes, it can create a lot of administrative busywork. This can cause HR and IT to struggle to coordinate the who-what-where of technical staff termination. Effective offboarding of technical staff is a dance between HR, IT, and management.
In organizations with a well-coordinated offboarding strategy:
- Teams establish a clearly defined process in advance.
- HR supports DevOps by suspending SSO access.
- Engineers and technical staff delete sensitive infrastructure credentials.
- Automation reduces workload while maintaining security.
- A final audit ensures that infrastructure is secure.
This is where the checklist comes in.
Technical Staff Offboarding Steps
Use this checklist whenever a technical employee leaves the organization:
- Inform HR as soon as termination occurs.
- Revoke Identity provider (IdP) and single sign-on (SSO) access.
- Remove access to databases, servers, and Kubernetes.
- Suspend access to SaaS accounts.
- Terminate VPN and employee remote access.
- Reset shared passwords.
- Forward employee email.
- Update system ownership.
- Recover company devices and physical assets.
- Back up local files and delete suspended accounts, per company policy.
- Reassign employee vendor licenses based on role.
- Regularly review access logs to ensure nothing slips through.
- Conduct an exit interview.
- Express thanks for the employee’s contributions, and part on good terms!
Make Offboarding Even Easier: Automate Offboarding with StrongDM
StrongDM can automate and consolidate your checklist into a simpler offboarding process. That means fewer errors, safer data, and happier employees in HR and DevOps. With StrongDM, you can:
- Extend your SSO to centrally manage infrastructure access.
By extending your SSO to manage infrastructure access, you can consolidate the many steps involved in revoking access to servers, Kubernetes, and databases across all platforms. When offboarding technical employees with far-reaching access, this is a huge timesaver.
Fair.com, an automotive fintech company, uses StrongDM to simplify the offboarding process for technical staff that need access to databases, servers, and Kubernetes clusters. The company no longer distributes underlying keys or credentials to staff but relies on their SSO to authenticate to any database, server, or K8s cluster.
- Revoke access to all infrastructure in one click.
MediaOS, which manages content for Hearst’s 21 magazines, including Elle, Cosmopolitan, and Esquire, uses StrongDM to replace a labor-intensive staff termination process. In fact, with StrongDM, MediaOS offboards IT staff in just 60 seconds.
- Eliminate administrative busywork.
StrongDM reduces administrative overhead by replacing disparate actions, scripts, and stitched-together systems with a unified, automated tool.
MakeSpace used StrongDM to replace a dozen scripts with a single command when offboarding technical staff. Now, MakeSpace can enforce the principle of least privilege (PoLP) without burdening the engineering team with administrative busywork.
- Minimize the risk of data exposure by enforcing PoLP.
Successful offboarding begins with thoughtful onboarding, which can be simplified by using role-based access control and the principle of least privilege.
MediaOS at Hearst, simplified both onboarding and offboarding using StrongDM. The DevOps team simply invites a new hire to the StrongDM platform and assigns a role. From there, the hire inherits all appropriate database permissions, and revoking these permissions is also just as easy.
- Maintain an audit trail of who did what, when, and where.
A final step in the offboarding process is regular auditing. You need to know if you are missing or forgetting something that leaves your infrastructure vulnerable.
StrongDM provides an audit trail to everything employees, vendors, and service accounts access. That means you can offboard with confidence.
Get the Checklist. Then Start Automating.
Bad actors and disgruntled employees will always pose a threat to data security. However, simplifying and auditing your termination process will help you mitigate risk and ease administrative burdens, making IT offboarding easy, fast, and painless.
Getting started is as easy as downloading the technical staff offboarding checklist.
How about an onboarding checklist? We have that as well! Find the onboarding checklist here.
Want to simplify offboarding even more? Book a demo of StrongDM.
To learn more about how StrongDM helps companies with offboarding, make sure to check out our Offboarding Use Case.
About the Author
💙 this post?
Then get all that StrongDM goodness, right in your inbox.
You May Also Like
Privileged Identity Management (PIM) is a complex cybersecurity approach. But it’s the only proven method you can use to lock down access and protect your precious resources. It can help you keep cybercriminals out and ensure that even your trusted users can’t accidentally—or intentionally—jeopardize your system’s security.
IGA (Identity Governance and Administration) manages user identities and access across the organization, ensuring proper access and compliance. PAM (Privileged Access Management) secures privileged accounts with elevated permissions by using measures like credential vaulting and session monitoring to prevent misuse. While IGA handles overall user access, PAM adds security for the most sensitive accounts.
In essence, legacy PAM solutions over-index on access. StrongDM uses the principles of Zero Trust to evaluate and govern every action, no matter how minor - where each command, query, or configuration change is evaluated in real-time against dynamic policies that adapt to the context of the user, the sensitivity of the action, and the prevailing threat landscape.
The way that people work continues to evolve, and as a result, so do the ways that they must authenticate into their organization’s resources and systems. Where once you simply had to be hardwired into the local office network, now you must expand your perimeter to include remote and hybrid workforces, on-prem and cloud environments, and take into account a growing list of factors that impact how and where people access critical company resources.