1. A method for implementing security in Application Security Environments in computers where an Application Security Environment is an environment in which one or more processes/tasks can be run and each Application Security Environment is owned by a user or a user group, and more particularly, controlling privileged operations and access to mass-memory devices from processes/threads running in an Application Security Environment by: i. Using a device supporting one or more Application Security Environments and one or more states for each supported Application Security Environment; This device is referred to as Application Security Environment Protection Device or ASEPDevice; The state of an Application Security Environment is referred to as Application Security Environment State. ii. The state of the ASEPDevice corresponding to an Application Security Environment is controlled by manual action by a user; The manual action by a user on the ASEPDevice is referred to as Application Security Environment Protection Manual Action or ASEPManualAction; iii. Where each state of an Application Security Environment corresponds to or maps to a set of privileges that the processes/tasks/threads running in that Application Security Environment have when that Application Security Environment is in that state. This mapping is referred to as Application Security Environment State Mapping. iv. The user or members of the user group who own an Application Security Environment are referred to as Application Security Environment Owners or ASEOs. v. Preferably, in addition to supporting ASEPManualAction that allows a user to the change the state of an Application Security Environment, an ASEPDevice supporting ASEPManualAction that allows a user to: a. Create or delete one or more users or b. Create or delete one or more user groups or c. Create or delete one or more Application Security Environments for a user or a user group or d. Create or delete one or more Application Security Environment States for an Application Security Environment or e. Add users to or remove users from a user group or f. Divide mass-memories into Regions which can be protected by ASEPDevices or g. Assign privileges to users and user groups including access to Regions of mass-memories or h. Create or modify or delete one or more Application Security Environment State Mappings for an Application Security Environment; iv. Optionally, some ASEPDevices allowing the ASEPManualAction to also select the user who performs that ASEPManualAction. In this case, the user name or the user identifier is also placed into registers/memory readable by the computer to which the ASEPDevice is attached along with other information about the ASEPManualAction. v. Every Application Security Environment being uniquely identifiable; Preferably, each Application Security Environment having a unique identifier in a computer; vi. A software in the computer to which the ASEPDevice is attached, authenticating the user who entered an ASEPManualAction and processing requests from the ASEPDevice; This software is referred to as ASEPSoftware; The ASEPSoftware and ASEPDevice discarding/rejecting the operation requested by an ASEPManualAction if the authentication of the user fails; vii. The ASEPSoftware or the ASEPDevice validating an operation requested by an ASEPManualAction and discarding/rejecting the operation if it is not a valid operation; viii. If an operation attempts to create or modify an Application Security Environment State Mapping in such a way that the set of privileges corresponding to or mapping to the Application Security Environment State exceed the privileges of the user or the user group who-owns the Application Security Environment, it is an invalid operation; ix. The ASEPSoftware or the ASEPDevice verifying whether an operation requested by an ASEPManualAction has conflict with any of the ongoing operations, employing a conflict resolution strategy as applicable such that no operations which are active at the same time have conflicts with each other; The conflict resolution strategy may involve discarding some operations or queuing-some operations or marking some operations for discarding at a later time. x. The ASEPDevice communicating the operation requested by an ASEPManualAction and any status changes to the operations requested by the ASEPManualAction to the ASEPSoftware using registers/memory readable by the computer to which the ASEPDevice is attached; Preferably, these registers/memory are not writable by the computer; xi. The ASEPSoftware sending commands to the ASEPDevice by writing into registers/memory in the ASEPDevice where these registers/memory are writable by the computer to which the ASEPDevice is attached; xii. Preferably, the ASEPDevice and ASEPSoftware using a unique identifier to identify an operation requested by an ASEPManualAction; xiii. Preferably, an ASEPDevice device driver processing the interrupts from one or more ASEPDevices and reading the operation requested or any status change for the operation requested by each ASEPManualAction from an ASEPDevice by reading registers/memory in the ASEPDevice; The ASEPDevice device driver sending the operation requested or any status change for the operation requested by each ASEPManualAction along with the unique identifier for the operation requested by the ASEPManualAction to the ASEPSoftware; The ASEPDevice device driver sending commands from the ASEPSoftware to an ASEPDevice by writing into the ASEPDevice registers/memory; Where the ASEPDevice device driver is the software component that controls the ASEPDevice; xiv. The ASEPSoftware sending a command to perform or discard/reject an operation; If the ASEPSoftware commands the ASEPDevice to perform an operation, the ASEPDevice performing an operation provided it is not marked for discarding due to conflict with an operation from another ASEPManualAction; If the ASEPSoftware commands the ASEPDevice to discard the operation, the ASEPDevice discarding the operation; xv. The ASEPSoftware sending a command to discard/reject an operation if user authentication for an ASEPManualAction fails or in the case where the ASEPSoftware is doing validation of the operation and the operation is invalid or in the case where ASEPSoftware is doing operation conflict resolution and the operation has conflict with another operation and the operation is selected for discarding/rejection by the operation conflict resolution strategy; xvi. The ASEPSoftware performing clean up required for an operation if it is not identified for discarding/rejection; The clean up involves blocking all processes/tasks that may impact the clean state from running and updating buffers and data structures; xvii. The ASEPSoftware sending a command to perform an operation to the ASEPDevice if the operation is not discarded/rejected and the clean up for the operation is completed; xviii. The ASEPDevice updating its registers/memory readable by the computer to which it attached, when an operation is rejected or completed indicating status; xix. The ASEPSoftware releasing the block for processes/tasks which were blocked from running for an operation to complete, after that operation is completed or discarded/rejected by the ASEPDevice; xx. The configuration used by the ASEPSoftware and ASEPDevices consisting of: a. The list of users; b. The list of user groups; c. The list of users in each user group; d. The privileges for each user and each user group; e. The list of Application Security Environments owned by each user or user group; f. The list of states for each Application Security Environment; g. The list of Regions of mass-memories protected by the ASEPDevices; h. The Application Security Environment State Mapping for each Application Security Environment State; xxi. Preferably, the configuration is stored in the ASEPDevices and the ASEPDevices are capable of identifying the current set of privileges of an Application Security Environment based on the current state of that Application Security Environment; xxii. Preferably, a computer software module that enforces access restrictions, reading ASEPDevice registers/memory to verify whether a privileged operation requested by a process/task/thread is permissible as per the Application Security Environment State Mapping for the current state of the Application Security Environment; These software modules that use the privileges corresponding to or mapped to the current state of an Application Security Environment to implement access protection are referred to as ASEPImplementers; xxiii. Optionally, the ASEPImplementers reading ASEPDevice registers/memory to fetch the current state of the Application Security Environment and the configuration containing the Application Security Environment State Mapping for the current state of the Application Security Environment and enforcing privileges based the current state of the Application Security Environment and the configuration; xxiv. Preferably, the ASEPImplementers reading the ASEPDevice registers/memory to read the current set of privileges that the processes/tasks/threads running in the Application Security Environment have corresponding to the current state of that Application Security Environment; xxv. When the configuration corresponding to the current state of the Application Security Environment does not allow a privileged operation requested by a process/task/thread in the Application Security Environment, the ASEPImplementer putting that process/task/thread in an error state; xxvi. When the configuration corresponding to the current state of the Application Security Environment allows a privileged operation requested by a process/task/thread in the Application Security Environment, the ASEPImplementer allowing the process/task/thread to perform the privileged operation; xxvii. Preferably, mass-memories are divided into Regions such that read or write access to these Regions are part of privileges that can be mapped to an Application Security Environment State; xxviii. A user or a user group having access to one or more of these Regions of a mass memory or mass memories; The access being further restricted to processes/tasks/threads in Application Security Environments owned by the user or the user group based on the current state of the Application Security Environment and the privilege configuration corresponding to the current Application Security Environment State; xxix. Preferably., when a process/task/thread in an Application Security Environment does a file operation permitted by file permissions that maps to a buffer in the file system buffer cache, the file system verifying whether the read or write access to the Region of mass-memory required by the file operation is permitted by the current set of privileges corresponding to the current state of the Application Security Environment; If the access is not permitted to the Region of mass-memory, the file system returning an error to the process/task/thread that attempted to do the file operation; If the access is permitted, the file system allowing the operation to continue; xxx. Preferably, a file system tagging a read or write request to read or write to a Region in a mass-memory with an identifier for the Application Security Environment so that the storage components below the file system or mass-memory device controllers can verify whether that Application Security Environment has sufficient privileges to do the operation in its current state; xxxi. Preferably-, when a process/task/thread in an Application Security Environment performs a raw disk read or write, the operating system tagging the raw disk read or write request with the identifier of the Application Security Environment so that storage components or a mass-memory device controller can enforce access protection based on the current state of that Application Security Environment.