Level B is the first to require Mandatory Protection. Because the higher levels also
inherit the requirements of all lower levels, level A also requires Mandatory Protection.
The following answers are incorrect:
B and C. Is incorrect because Mandatory Protection is not required until level B, Level C is a lower
level.
A, B, and C. Is incorrect because Mandatory Protection is not required until level B, Level C is a
lower level.
B and D. Is incorrect because Mandatory Protection is not required until level B, Level D is a lower
level.
One of the first accpted evaluation standards was the Trusted Computer Security Evaluation
Criteria or TCSEC. The Orange Book was part of this standard that defines four security divisions
consisting of seven different classes for security ratings. The lowest class offering the least
protection is D - Minimal protection. The highest classification would be A1 offering the most
secure environment. As you go to the next division and class you inherit the requirements of the
lower levels. So, for example C2 would also incorporate the requirements for C1 and D.
The divisions and classes are:
D - Minimal protection
C - Discretionary protection
C1 - Discretionary Security Protection
C2 - Controlled Access Protection
B - Mandatory Protection
B1 - Labeled Security
B2 - Structured Protection
B3 - Security Domains
A - Verified Protection
A1 - Verified Design
Wikipedia: "TCSEC was replaced with the development of the Common Criteria international
standard originally published in 2005."
References:
OIG CBK, Security Architecture and Design (pages 329 - 330)
AIO, 3rd Edition, Security Models and Architecture (pages 302 - 306)
AIO, 4th Edition, Security Architecture and Design, pp357-361.
Wikipedia - http://en.wikipedia.org/wiki/TCSEC#Divisions_and_Classes
DOD TCSEC - http://www.cerberussystems.com/INFOSEC/stds/d520028.htm
NSI reference for Orange book: http://nsi.org/Library/Compsec/orangebo.txt

SHA was designed by NSA and published by NIST to be used with the Digital Signature Standard (DSS).
SHA was designed to be used in digital signatures and was developed when a more secure hashing algorithm was required for U.S. government applications.
SHA produces a 160-bit hash value, or message digest.
This is then inputted into an asymmetric algorithm, which computes the signature for a message. SHA is similar to MD4. It has some extra mathematical functions and produces a 160-bit hash instead of a 128-bit hash like MD5, which makes it more resistant to brute force attacks, including birthday attacks.
SHA was improved upon and renamed SHA-1. Recently, newer versions of this algorithm have been developed and released such as SHA2 which has the following hash length: SHA-256, SHA384, and SHA-512.
NOTE: Very recently SHA-3 has also been releasd but it is to new to be in the CBK.
The following answers are incorrect: RSA Diffie Hellman
Elliptic Curve Cryptography(ECC)
All of the choices above are examples of an Asymmetric algorithm
The following reference(s) were/was used to create this question:
Harris, Shon (2012-10-18). CISSP All-in-One Exam Guide, 6th Edition (p. 827). McGraw-Hill .
Kindle Edition.

The IAB document, Ethics and the Internet (RFC 1087) listed behaviors as unethical that: Seek to gain unauthorized access to the resources of the Internet Destroy the integrity of computer-based information Disrupt the intended use of the Internet Waste resources such as people, capacity and computers through such actions Compromise the privacy of users Involve negligence in the conduct of Internetwide experiments The other answers are taken from the Code of Fair Information Practices of the U.S. Department of Health, Education of Welfare.

Detective control helps identify an incident's activities and potentially an intruder For your exam you should know below information about different security controls
Deterrent Controls Deterrent Controls are intended to discourage a potential attacker. Access controls act as a deterrent to threats and attacks by the simple fact that the existence of the control is enough to keep some potential attackers from attempting to circumvent the control. This is often because the effort required to circumvent the control is far greater than the potential reward if the attacker is successful, or, conversely, the negative implications of a failed attack (or getting caught) outweigh the benefits of success. For example, by forcing the identification and authentication of a user, service, or application, and all that it implies, the potential for incidents associated with the system is significantly reduced because an attacker will fear association with the incident. If there are no controls for a given access path, the number of incidents and the potential impact become infinite. Controls inherently reduce exposure to risk by applying oversight for a process. This oversight acts as a deterrent, curbing an attacker's appetite in the face of probable repercussions. The best example of a deterrent control is demonstrated by employees and their propensity to intentionally perform unauthorized functions, leading to unwanted events. When users begin to understand that by authenticating into a system to perform a function, their
activities are logged and monitored, and it reduces the likelihood they will attempt such an action.
Many threats are based on the anonymity of the threat agent, and any potential for identification
and association with their actions is avoided at all costs.
It is this fundamental reason why access controls are the key target of circumvention by attackers.
Deterrents also take the form of potential punishment if users do something unauthorized. For
example, if the organization policy specifies that an employee installing an unauthorized wireless
access point will be fired, that will determine most employees from installing wireless access
points.
Preventative Controls
Preventive controls are intended to avoid an incident from occurring. Preventative access controls
keep a user from performing some activity or function. Preventative controls differ from deterrent
controls in that the control is not optional and cannot (easily) be bypassed. Deterrent controls work
on the theory that it is easier to obey the control
rather than to risk the consequences of bypassing the control. In other words, the power for action
resides with the user (or the attacker). Preventative controls place the power of action with the
system, obeying the control is not optional. The only way to bypass the control is to find a flaw in
the control's implementation.
Compensating Controls
Compensating controls are introduced when the existing capabilities of a system do not support
the requirement of a policy. Compensating controls can be technical, procedural, or managerial.
Although an existing system may not support the required controls, there may exist other
technology or processes that can supplement the existing environment, closing the gap in
controls, meeting policy requirements, and reducing overall risk.
For example, the access control policy may state that the authentication process must be
encrypted when performed over the Internet. Adjusting an application to natively support
encryption for authentication purposes may be too costly. Secure Socket Layer (SSL), an
encryption protocol, can be employed and layered on top of the authentication process to support
the policy statement.
Other examples include a separation of duties environment, which offers the capability to isolate
certain tasks to compensate for technical limitations in the system and ensure the security of
transactions. In addition, management processes, such as authorization, supervision, and
administration, can be used to compensate for gaps in the access control environment.
Detective Controls
Detective controls warn when something has happened, and are the earliest point in the post-
incident timeline. Access controls are a deterrent to threats and can be aggressively utilized to
prevent harmful incidents through the application of least privilege. However, the detective nature
of access controls can provide significant visibility into the access environment and help
organizations manage their access strategy and related security risk.
As mentioned previously, strongly managed access privileges provided to an authenticated user offer the ability to reduce the risk exposure of the enterprise's assets by limiting the capabilities that authenticated user has. However, there are few options to control what a user can perform once privileges are provided. For example, if a user is provided write access to a file and that file is damaged, altered, or otherwise negatively impacted (either deliberately or unintentionally), the use of applied access controls will offer visibility into the transaction. The control environment can be established to log activity regarding the identification, authentication, authorization, and use of privileges on a system. This can be used to detect the occurrence of errors, the attempts to perform an unauthorized action, or to validate when provided credentials were exercised. The logging system as a detective device provides evidence of actions (both successful and unsuccessful) and tasks that were executed by authorized users.
Corrective Controls When a security incident occurs, elements within the security infrastructure may require corrective actions. Corrective controls are actions that seek to alter the security posture of an environment to correct any deficiencies and return the environment to a secure state. A security incident signals the failure of one or more directive, deterrent, preventative, or compensating controls. The detective controls may have triggered an alarm or notification, but now the corrective controls must work to stop the incident in its tracks. Corrective controls can take many forms, all depending on the particular situation at hand or the particular security failure that needs to be dealt with.
Recovery Controls Any changes to the access control environment, whether in the face of a security incident or to offer temporary compensating controls, need to be accurately reinstated and returned to normal operations. There are several situations that may affect access controls, their applicability, status, or management. Events can include system outages, attacks, project changes, technical demands, administrative gaps, and full-blown disaster situations. For example, if an application is not correctly installed or deployed, it may adversely affect controls placed on system files or even have default administrative accounts unknowingly implemented upon install. Additionally, an employee may be transferred, quit, or be on temporary leave that may affect policy requirements regarding separation of duties. An attack on systems may have resulted in the implantation of a Trojan horse program, potentially exposing private user information, such as credit card information and financial data. In all of these cases, an undesirable situation must be rectified as quickly as possible and controls returned to normal operations.
The following answers are incorrect: Deterrent - Deterrent controls are intended to discourage a potential attacker Preventive - Preventive controls are intended to avoid an incident from occurring Compensating - Compensating Controls provide an alternative measure of control
The following reference(s) were/was used to create this question:
CISA Review Manual 2014 Page number 44 and Official ISC2 CISSP guide 3rd edition Page number 50 and 51