CSSA ICS/SCADA Security Architect preparation common mistakes
CSSA ICS/SCADA Security Architect preparation · Understand the traps and how to avoid them.
ot-architecture: Calling every blocked communication a safe process condition.
Network access and physical safety are different properties.
What to do instead
Verify the actual process response and appropriate engineered protections with competent operational input.
ot-architecture: Treating one tool or score as a complete authorization for production action.
Technical capability and vulnerability severity do not establish operational permission or acceptable consequences.
What to do instead
Use actual scope, version, exposure, process risk and the responsible approved change or assessment process.
ot-safe-operations: Calling every blocked communication a safe process condition.
Network access and physical safety are different properties.
What to do instead
Verify the actual process response and appropriate engineered protections with competent operational input.
ot-safe-operations: Treating one tool or score as a complete authorization for production action.
Technical capability and vulnerability severity do not establish operational permission or acceptable consequences.
What to do instead
Use actual scope, version, exposure, process risk and the responsible approved change or assessment process.
Assuming a firewall or IDS alone stops an attack, and choosing 'install a firewall' as the fix for problems that are actually about inspection of encrypted traffic, lateral movement inside a trusted zone, or application-layer payloads.
Perimeter devices are the most familiar control in the network domain, and candidates default to them because they can picture the device, not because it addresses the specific failure described.
What to do instead
For each network scenario, name the layer first (packet, session, application) and the zone (outside, DMZ, internal). Then ask whether the described traffic crosses a boundary at all; if it is internal east-west traffic or encrypted payload, a perimeter filter is the wrong answer and segmentation, inspection, or endpoint controls are correct.
Confusing authentication with authorisation and assigning the wrong control to a scenario, for example answering 'multi-factor authentication' when the question is about limiting what a logged-in user can reach.
Both live in the same identity domain and both are described with similar vocabulary (access, permissions, credentials), so candidates pattern-match on 'access' and pick the wrong half of the pair.
What to do instead
Distinguish identity verification from the authorization decision for the actual request. Some resources allow unauthenticated public access, and authorization can be checked repeatedly during a session. Roles and permissions concern allowed actions rather than merely proving who supplied a credential.
Treating symmetric and asymmetric keys as interchangeable and choosing the wrong key for a task, such as using a public key to decrypt a password vault or a private key to encrypt bulk data.
The key pair vocabulary is learned as a pair of words rather than as a workflow, so candidates cannot reconstruct who holds which key and what each operation achieves.
What to do instead
Draw the two-party diagram once from memory: sender encrypts with the recipient's public key, recipient decrypts with their own private key; sender signs with their own private key, verifier checks with the sender's public key. Rehearse it until you can derive any key question from the diagram rather than recall.
Answering control-design questions with control-testing or monitoring activities, and vice versa.
Control design, operating effectiveness, and continuous monitoring appear together in real programmes, so candidates conflate them. Exam stems often hinge on whether a control exists on paper versus whether it actually worked in practice.
What to do instead
Label the question first: 'does the control exist and is it designed suitably?' (design), 'did it operate as intended over the period?' (effectiveness), or 'is it still working now?' (monitoring). Then eliminate options that answer a different one of those three questions.
Assuming an emerging-technology risk should be avoided or blocked until it is fully understood, rather than managed through incremental assessment and monitoring.
Uncertainty feels like a reason to stop, and regulatory or security caution reinforces that instinct. CRISC expects emerging risk to be assessed, piloted, and monitored with defined triggers, not reflexively prohibited.
What to do instead
When a stem describes new or evolving technology with limited information, prefer the option that combines a bounded assessment with defined monitoring triggers and review points. Treat 'prohibit until proven safe' and 'proceed without assessment' as the two distractors.
Choosing the answer that describes the 'best practice' control rather than the answer that reflects what the business has decided it can tolerate.
Candidates transfer an audit or security-engineering mindset into CRISC, where the risk practitioner's job is to inform and enable a business decision, not to impose the safest option. Options containing words like 'eliminate', 'ensure', 'mandate', or 'all risk is avoided' feel rigorous but are usually wrong.
What to do instead
Before answering, classify the question: is it asking what the risk practitioner should DO next, or what the business should DECIDE? If the stem involves tolerance, appetite, or trade-offs, eliminate any option that removes the business's choice and prefer the option that quantifies, communicates, and escalates.
Jumping to a response (mitigate, transfer, avoid, accept) before establishing or confirming the risk context and performing the assessment.
Experienced practitioners recognise the response immediately in the scenario and answer it, skipping the earlier step the question actually asks about. CRISC questions are sequence-sensitive; the 'next' step is almost always the earliest incomplete step in the risk process.
What to do instead
Apply a fixed sequence check on every stem: identify/context, then analyse/assess, then evaluate against appetite, then respond, then monitor and report. Ask 'what has explicitly already happened in this stem?' and select the first action that comes after it.
Choosing quantitative risk analysis over qualitative without testing whether the data needed for quantification exists or whether the decision requires it.
Quantification is presented as more mature, so candidates assume it is always the better answer. In practice, forcing quantification on sparse or unreliable data produces false precision and is a poor recommendation.
What to do instead
Ask what data is available and what decision is being made. If the stem shows missing historical data, a novel risk, or a fast screening decision, select qualitative or semi-quantitative; select quantitative when reliable loss data or actuarial input exists and the decision involves material financial trade-offs.