An advantage of an effective release control strategy from a configuration control standpoint is that it ensures that a trace for all deliverables is maintained and auditable. Release control is a process that manages the distribution and installation of software releases into the operational environment. Configuration control is a process that maintains the integrity and consistency of the software configuration items throughout the software development life cycle. An effective release control strategy can help to ensure that a trace for all deliverables is maintained and auditable, which means that the origin, history, and status of each software release can be tracked and verified. This can help to prevent unauthorized or incompatible changes, as well as to facilitate troubleshooting and recovery. Ensuring that there is no loss of functionality, allowing for future enhancements, and enforcing backward compatibility are not advantages of release control from a configuration control standpoint, but from a functionality or performance standpoint. References: CISSP All-in-One Exam Guide, Eighth Edition, Chapter 8: Software Development Security, page 969; Official (ISC)2 Guide to the CISSP CBK, Fifth Edition, Chapter 7: Software Development Security, page 895.

The Information Security Department must verify that the service provider will impose controls and protections that meet or exceed the current systems controls and produce audit logs as verification. This is to ensure that the service provider will maintain or improve the security posture of the organization, and that the organization will be able to monitor and audit the service provider's performance and compliance. The service provider's policies may or may not be consistent with ISO/IEC27001, but this is not a mandatory requirement, as long as the service provider can meet the organization's security needs and expectations. The service provider may or may not segregate the data within its systems, depending on the type and sensitivity of the data, and the contractual and regulatory obligations. The service provider's policies may differ from the organization's current policies, as long as they can meet the requirements imposed by the new environment, and are agreed upon by both parties. References: 1: How to Choose a Managed Security Service Provider (MSSP)22: 10 Questions to Ask Your Managed Security Service Provider3

The Trusted Computing Base (TCB) The totality of protection mechanisms within a computer system, including hardware, firmware, and software, the combination of which is responsible for enforcing a security policy. A TCB consists of one or more components that together enforce a unified security policy over a product or system. The ability of a trusted computing base to correctly enforce a security policy depends solely on the mechanisms within the TCB and on the correct input by system administrative personnel of parameters (e.g., a users clearance) related to the security policy. *Answer "A computer that controls all access to objects by subjects" describes the reference monitor concept. The reference monitor is an access control concept that refers to an abstract machine that mediates all accesses to objects by subjects. The Security Kernel consists of the hardware, firmware, and software elements of a Trusted Computing Base (or Network Trusted Computing Base partition) that implement the reference monitor concept. It must mediate all accesses, be protected from modification, and be verifiable as correct. *Answer "A piece of information that represents the security level of an object" refers to a sensitivity label. Asensitivity label is a piece of information that represents the extra security level of an object and describes the sensitivity (e.g., classification) of the data in the object. Sensitivity labels are used by the TCB as the basis for mandatory access control decisions. *Answer "Formal proofs used to demonstrate the consistency between a systems specification and a security model" describes formal verification. This is the process of using formal proofs to demonstrate the consistency (design verification) between a formal specification of a system and a formal security policy model or (implementation verification) between the formal specification and its program implementation. Source: DoD 5200.28-STD Department of Defense Trusted Computer System Evaluation Criteria

The type of negative testing that is exemplified by running tests to ensure that user entry fields will not accept invalid input of any length is allowed number of characters. Negative testing is a type of software testing that aims to verify the behavior and the performance of the software when it encounters invalid, unexpected, or erroneous input or conditions. Negative testing can help identify the defects, the errors, the exceptions, or the failures of the software, and improve the quality, the security, and the robustness of the software. Allowed number of characters is a type of negative testing that checks the user entry fields for the maximum or the minimum number of characters that they can accept or reject. Allowed number of characters can help prevent the buffer overflow, the data truncation, or the data corruption issues that may occur when the user entry fields receive input that exceeds or falls short of the expected length. Allowed number of characters can also help validate the format, the syntax, or the type of the input that is entered by the user. References: CISSP All-in-One Exam Guide, Eighth Edition, Chapter 8: Software Development Security, page 440. Free daily CISSP practice questions, Question 5.