Dual authorization requires two distinct approving authorities to approve the use of an application command prior to it being invoked. This capability is typically reserved for specific application functionality where the application owner, data owner, or organization requires an additional assurance that certain application commands are only invoked under the utmost authority. When a policy is defined stating that certain commands contained within an application require dual-authorization before they may be invoked, or when an organization defines a set of application related privileged commands requiring dual authorization, the application must support those requirements.
Due to potential delays in obtaining secondary approvals prior to executing commands, dual authorization mechanisms should not be utilized when an immediate response is necessary in order to ensure public and/or environmental safety. If, after due consideration, it is determined the benefit of dual authorization outweighs identified risks, the organization must establish documented procedures, assign specific personnel to provide approvals, and establish operational exercises assuring that any risks to public safety, environmental safety or otherwise, are minimized.
If dual authorization is not implemented for functionality where it is required, that functionality may be accessed and utilized without proper authorization. This could result in serious consequences to the information system as dual authorization should be utilized only for application functionality for which the utmost authority is required.
|