The answer is to configure the IdP to reject assertions with a stale timestamp using the Conditions element. This is correct because the SAML Conditions element explicitly defines the assertion’s validity window through the NotBefore and NotOnOrAfter attributes, allowing the identity provider to enforce SAML Conditions element assertion validity by rejecting any assertion whose timestamp falls outside that window. On the CISSP exam, this tests your understanding of federated identity security controls, often appearing in questions about replay attacks or stale assertions—a common trap is to suggest increasing the validity window or relying on partner-side updates, which weakens security. Remember the memory tip: “Conditions control the clock—NotBefore starts it, NotOnOrAfter stops it.”
CISSP Identity and Access Management Practice Question
This CISSP practice question tests your understanding of identity and access management. The scenario asks you to isolate a root cause — eliminate options that address a different problem before choosing. After answering, compare your reasoning against the explanation and wrong-answer breakdown below. Once you have made your selection, read the full explanation to reinforce the concept and understand why each distractor is designed to mislead on exam day.
An organization uses a federated identity model with multiple external partners. The identity provider (IdP) notices that some partners are sending outdated SAML assertions. What is the best way to mitigate this issue?
Clue words in this question
Noticing these words before you look at the options changes how you read each choice.
Clue: "best"
Why it matters: Signals that multiple options may be partially correct. Choose the option that most directly solves the exact problem described, not the one that sounds most complete.
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Configure the IdP to reject assertions with a stale timestamp using the Conditions element.
Option C is correct because the SAML Conditions element explicitly defines the validity window for an assertion using NotBefore and NotOnOrAfter attributes. By configuring the IdP to validate these timestamps and reject assertions that fall outside the window, the organization directly enforces assertion freshness without relying on partner-side changes or weakening security.
Key principle: Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
✗
Require partners to include a timestamp in the assertion.
Why it's wrong here
Timestamps are usually already included; the issue is validation.
✗
Increase the NotBefore and NotOnOrAfter time window.
Why it's wrong here
This reduces security by allowing older assertions.
✓
Configure the IdP to reject assertions with a stale timestamp using the Conditions element.
Why this is correct
This enforces assertion freshness and mitigates replay attacks.
Clue confirmation
The clue word "best" in the question point toward this answer.
Related concept
Read the scenario before looking for a memorised answer.
✗
Implement short-lived assertions and require re-authentication.
Why it's wrong here
This is a good practice but does not directly solve the issue of partners sending outdated ones.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates confuse 'requiring a timestamp' (which is already present) with 'validating the timestamp' (which is the actual control), or they mistakenly think widening the time window is a mitigation when it actually increases risk.
Detailed technical explanation
How to think about this question
The SAML 2.0 Conditions element (section 2.5.1.1 of the SAML Core spec) allows the IdP to specify NotBefore and NotOnOrAfter timestamps, and the relying party (or IdP in a proxy scenario) must check these. A common subtlety is that clock skew between partners can cause valid assertions to be rejected; the IdP can configure a small tolerance (e.g., 5 minutes) within the Conditions check to handle this without expanding the overall window. In real-world federations, this is critical for compliance with standards like NIST SP 800-63C, which requires short assertion lifetimes.
KKey Concepts to Remember
Read the scenario before looking for a memorised answer.
Find the constraint that changes the correct option.
Eliminate answers that are true in general but not in this case.
TExam Day Tips
→Watch for words such as best, first, most likely and least administrative effort.
→Review why wrong options are wrong, not only why the correct option is correct.
Key takeaway
Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Real-world example
How this comes up in practice
A security analyst at a medium-sized enterprise encounters this scenario during an investigation or architecture review. The correct answer reflects best practice for the specific threat or control described. Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option. Security exam questions test whether you can match controls to threats in context — not just recall definitions.
Related glossary terms
Concepts from this question explained
These glossary pages explain the core terms tested in this CISSP question in full detail.
Identity and Access Management — This question tests Identity and Access Management — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: Configure the IdP to reject assertions with a stale timestamp using the Conditions element. — Option C is correct because the SAML Conditions element explicitly defines the validity window for an assertion using NotBefore and NotOnOrAfter attributes. By configuring the IdP to validate these timestamps and reject assertions that fall outside the window, the organization directly enforces assertion freshness without relying on partner-side changes or weakening security.
What should I do if I get this CISSP question wrong?
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
Are there clue words in this question I should notice?
Yes — watch for: "best". Signals that multiple options may be partially correct. Choose the option that most directly solves the exact problem described, not the one that sounds most complete.
What is the key concept behind this question?
Read the scenario before looking for a memorised answer.
About these practice questions
Courseiva creates original exam-style practice questions with explanations and wrong-answer analysis. It does not publish real exam questions, exam dumps, or protected exam content. Learn why practice questions differ from exam dumps →
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
This CISSP practice question is part of Courseiva's free ISC2 certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the CISSP exam.
Question Discussion
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
Sign in to join the discussion.