Employee termination
Last updated: Nov 3, 2026
This document gives the details of the protocol that Fluid Attacks follows when a talent leaves the company.
High-level procedure
- The Administration team prepares the termination documents when they apply (for example, the letter of dismissal, reports, and the inventory list).
- Fluid Attacks removes the logical access of terminated employees. It deactivates their accounts in Okta, Time Doctor, Google Suite, EasyLlama, and the applications of their role.
- Fluid Attacks communicates with the applicable stakeholders and identifies hand-off plans when they apply.
- Terminated employees must return the hardware of Fluid Attacks. Fluid Attacks sanitizes the hardware as necessary.
- Fluid Attacks pays all the pending financial obligations, for example, expense reimbursements and the final payroll.
Logical access to systems
The Administrative Director asks for the deactivation of corporate systems through the Help channel. The Head of Technology or the Security Manager must deactivate all the other access that the terminated employee has because of their role. Fluid Attacks revokes the access to these systems:
- Okta
- Google Suite
- EasyLlama
- Time Doctor
- Iru (if applicable)
- Other tools and systems, in accordance with the role
Physical access
The Administrative Director asks for the deactivation of the laptop access.
Hardware return
The Administration team collects the hardware that Fluid Attacks gave to the talent:
- Laptop
- Keyboard
- Mouse
- All other devices from Fluid Attacks (if applicable)
Exit reminder
As part of the offboarding process, Fluid Attacks sends an email to the employees who leave on their last day. This email tells them about their security commitments after their departure, which they agreed to in a non-disclosure agreement. Fluid Attacks sends this message to their personal email address, because their Fluid Attacks account is deactivated. The reminder contains a statement similar to this one:
"You continue to be bound by the confidentiality agreement (NDA) that you signed during the onboarding process. This agreement includes these obligations:
- Keep all the proprietary information of Fluid Attacks confidential.
- Do not disclose customer data or sensitive information that you got during your employment.
- Do not keep company documents or data, in physical or electronic form."
Other secure authorization measures
Authorization for clients
The Fluid Attacks platform has role-based access control (RBAC) at the organization and group levels for each project to protect client data.
Endpoints
Fluid Attacks secures laptops and mobile phones with MDM, including disk encryption, EDR, vulnerability management, hardening Blueprints, removable media restrictions, auditing, and inventory controls.