Ransomware attackers specifically target and attempt to destroy backup systems to increase the probability of payment. Hardening your system is critical. Please ensure you have reviewed your platform security using the Security Hardening Checklist
Cohesity

COHESITY Documentation

Explore our documentation to get started, discover products & new features, access troubleshooting guides, register sources, platforms support.

Products
Data Security Alliance
Visit Cohesity.com
Demos
Support
Blogs
Developers
Partner Portals
Cohesity Community
© 2026 Cohesity, Inc. All Rights Reserved.
Terms of Use|
Privacy Policy|
Legal|
  1. Home
  2. NetBackup and NetBackup Appliances Hardening Guide
  3. Steps to protect Flex Appliance
  4. Managing multiperson authorization
  5. Multiperson authorization process workflow
NetBackup and NetBackup Appliances Hardening Guide

Multiperson authorization process workflow

The process workflow for multiperson authorization is as follows:

  1. A requester performs a critical operation using the Flex Appliance Console.

  2. A request is created.

  3. The request is pending for approval

  4. Approvers review the request.

  5. Approvers either approve or reject the request.

  6. After the quorum is reached, the request is scheduled by Flex Appliance and finally marked as Done after the execution.

  7. The request activity log, request, and response details can be viewed by the approver or the requester using the Flex Appliance Console on the Request management page.

  8. A request is expired after it ages beyond the expiration period. It has to be created again, if required.

  9. All requests in the Done, Rejected, Expired, and Canceled states are deleted when the retention period has elapsed.

  10. All requests in the Pending state are expired when they reach the expiration period.

Feedback

Was this page helpful?
Previous

Terminology

Next

Considerations for configuring multiperson authorization

Feedback

Was this page helpful?