Access revocation
Last updated: Nov 3, 2026
A talent can take leave for more than three days, go on vacation, or leave the company. In these cases, Fluid Attacks must revoke their access to the information and systems that are available to them. In the first two cases, Fluid Attacks gives the access again when the talent returns to work.
Fluid Attacks uses a three-step process for access revocation:
- Deactivation of the IAM account: The user loses access to all the company applications and client data. This includes the Fluid Attacks platform, email, and other applications.
- Removal of Git repository access: The user cannot see confidential information from the repository any more. This includes registry images, private issues, merge requests, and other information.
- Laptop lock: Fluid Attacks blocks the access to the laptop.
Easy access revocation is fundamental when an organization works with sensitive data. Thus, Fluid Attacks made this process as simple as possible.
This process must be complete in a 24-hour period.
Requirements
- 023. Terminate inactive user sessions
- 114. Deny access with inactive credentials
- 144. Remove inactive accounts periodically