Explanation/Reference:
Explanation:
B1: Labeled Security: Each data object must contain a classification label and each subject must have a clearance label. When a subject attempts to access an object, the system must compare the subject's and object's security labels to ensure the requested actions are acceptable. Data leaving the system must also contain an accurate security label. The security policy is based on an informal statement, and the design specifications are reviewed and verified.
This security rating is intended for environments that require systems to handle classified data.
Incorrect Answers:
A: Security labels are not required at level C2.
C: Security labels are required at level B2; however, they were introduced at level B1.
D: Security labels are required at level B3; however, they were introduced at level B1.
References:
Harris, Shon, All In One CISSP Exam Guide, 6th Edition, McGraw-Hill, New York, 2013, p. 395

The markup language that the organization's security personnel should use to support the integration of a service provider that authenticates users via the users' organization domain credentials is Security Assertion Markup Language (SAML). SAML is an XML-based standard that enables the exchange of authentication and authorization information between different entities, such as an identity provider (IdP) and a service provider (SP). SAML allows users to access multiple services with a single sign-on (SSO), without the need to create or manage separate accounts or credentials for each service. SAML uses assertions, which are statements that contain information about the user, such as the identity, attributes, or entitlements. The IdP generates and signs the assertions, and the SP validates and consumes the assertions. SAML can be used to implement federated identity management, which is a model that allows users to use their existing credentials from one domain to access resources from another domain. References: CISSP All-in-One Exam Guide, Chapter 5: Identity and Access Management, Section: Identity and Access Provisioning Lifecycle, pp. 423-424.

Explanation/Reference: