    
Раздел: Документация
0 ... 82 83 84 85 86 87 88 ... 117 FDPRIP.1 Subset residual information protection User application notes This component requires that, for a subset of the objects in the TOE, the TSF will ensure that there is no available residual information contained in a resource allocated to those objects or deallocated from those objects. Operations Selection: In FDPRIP.1.1, the PP/ST author should specify the event, allocation of the resource to or deallocation of the resource from, that invokes the residual information protection function. Assignment: In FDPRIP.1.1, the PP/ST author should specify the list of objects subject to residual information protection. FDPRIP.2 Full residual information protection User application notes This component requires that for all objects in the TOE, the TSF will ensure that there is no available residual information contained in a resource allocated to those objects or deallocated from those objects. Operations Selection: In FDPRIP.2.1, the PP/ST author should specify the event, allocation of the resource to or deallocation of the resource from, that invokes the residual information protection function. F.10 Rollback (FDP ROL) This family addresses the need to return to a well defined valid state, such as the need of a user to undo modifications to a file or to undo transactions in case of an incomplete series of transaction as in the case of databases. This family is intended to assist a user in returning to a well defined valid state after the user undoes the last set of actions, or, in distributed databases, the return of all of the distributed copies of the databases to the state before an operation failed. FDP RIP and FDP ROL conflict when FDP RIP enforces that the contents will be made unavailable at the time that a resource is deallocated from an object. Therefore, this use of FDP RIP cannot be combined with FDP ROL as there would be no information to roll back. FDP RIP can be used only with FDP ROL when it enforces that the contents will be unavailable at the time that a resource is allocated to an object. This is because the FDP ROL mechanism will have an opportunity to access the previous information that may still be present in the TOE in order to successfully roll back the operation. The rollback requirement is bounded by certain limits. For example a text editor typically only allows you roll back up to a certain number of commands. Another example would be backups. If backup tapes are rotated, after a tape is reused, the information can no longer be retrieved. This also poses a bound on the rollback requirement. FDPROL.1 Basic rollback User application notes This component allows a user or subject to undo a set of operations on a predefined set of objects. The undo is only possible within certain limits, for example up to a number of characters or up to a time limit. Operations Assignment: In FDPROL.1.1, the PP/ST author should specify the access control SFP(s) and/ or information flow control SFP(s) that will be enforced when performing rollback operations. This is necessary to make sure that roll back is not used to circumvent the specified SFPs. In FDPROL.1.1 the PP/ST author should specify the list of operations that can be rolled back. In FDPROL.1.1 the PP/ST author should specify the list of objects that are subjected to the rollback policy. In FDPROL.1.2 the PP/ST author should specify the boundary limit to which rollback operations may be performed. The boundary may be specified as a predefined period of time, for example, operations may be undone which were performed within the past two minutes. Other possible boundaries may be defined as the maximum number of operations allowable or the size of a buffer. FDPROL.2 Advanced rollback User application notes This component enforces that the TSF provide the capability to rollback all operations; however, the user can choose to rollback only a part of them. Operations Assignment: In FDPROL.2.1, the PP/ST author should specify the access control SFP(s) and/or information flow control SFP(s) that will be enforced when performing rollback operations. This is necessary to make sure that roll back is not used to circumvent the specified SFPs. In FDPROL.2.1 the PP/ST author should specify the list of objects that are subjected to the rollback policy. In FDPROL.2.2 the PP/ST author should specify the boundary limit to which rollback operations may be performed. The boundary may be specified as a predefined period of time, for example, operations may be undone which were performed within the past two minutes. Other possible boundaries may be defined as the maximum number of operations allowable or the size of a buffer. 0 ... 82 83 84 85 86 87 88 ... 117 |
