Cyber Risk Analyst
You tell the business what is risky, how much, and what to do about it.
Competency areas
- Security Control Assessment
- Cybersecurity Policy and Planning
- Technology Program Auditing
- Specialized practice
- Systems Authorization
Aramis:Current Daily
A short reading list for a Cyber Risk Analyst, under 30 minutes per edition.
2026-09-28. 2 minutes in total
Microsoft tells nonprofits their deleted M365 data isn't coming back
The Register, 2026-09-28. Read, 2 min.
Why it matters for this role: Microsoft's early deletion of nonprofit data it can neither recover nor list belongs in your SaaS risk scenarios as a vendor error, alongside the attack cases.
Sample questions
Three real questions from this role's assessment, with the answer, the reasoning, and the NICE statement each one measures. The full assessment draws from hundreds like these.
Sample question 1
Verano Pay, a fintech company, is wiring a third-party large language model into its fraud review workflow through new plugins that read transaction records and write to the internal case management system. Executive leadership asks the cyber risk analyst to develop a cybersecurity risk management plan for the integration before it goes live. Which deliverable best fulfills the request?
- A.Threats specific to the integration, such as prompt injection through case notes and plugin permission abuse, rated for likelihood and impact, with prioritized controls, named owners, and a reassessment schedule.
- B.A registration of the integration in the enterprise risk register under the existing third-party technology category, inheriting the data handling, access control, and incident response requirements the enterprise security policy already defines.
- C.A vendor agreement package covering uptime commitments, data processing terms, breach notification windows, and audit rights, negotiated with the model provider's counsel and reviewed annually at contract renewal.
- D.A pre-launch penetration test of the plugin layer, with remediation of critical and high findings gated before go-live and a retest scheduled at the first anniversary of the deployment.
Show the answer and reasoning
Correct answer: A
A risk management plan for a new integration names the threats that integration specifically introduces, rates their likelihood and impact, and assigns prioritized controls, owners, and a reassessment cadence; a language model wired into transaction data and case tools creates paths like prompt injection through case notes and plugin permission abuse that only an integration-specific assessment surfaces. Registering the integration under an existing third-party category inherits generic requirements written before this technology pattern existed and identifies none of its novel threat paths. The vendor agreement package sets contract terms; it is externally focused and leaves the company without its own assessment of likelihood, impact, or control ownership. The penetration test with a gated launch and anniversary retest is a control activity that produces point-in-time findings; it does not identify, prioritize, or assign ownership for risk between tests.
This question measures: T1265: Develop a cybersecurity risk management plan
Sample question 2
Novara Biotech is onboarding a new business unit, a contract research subsidiary that stores unpublished clinical trial data and connects to several external contract research organizations over site-to-site VPN links. Leadership asks you to develop a cybersecurity risk profile for this business unit ahead of its integration into the parent company's risk program. What should the risk profile primarily characterize?
- A.The unit's technical vulnerability state: the specific weaknesses surfaced by its most recent vulnerability scans and penetration tests, each ranked by CVSS severity, mapped to its exploitability and current patch status, and tracked against remediation deadlines, because the concentration of exploitable technical flaws is what most directly drives the unit's exposure ahead of integration.
- B.The unit's regulatory conformance: the clinical-data regulations and the data-protection clauses in its contracts with external research organizations, the control gaps found when auditing it against the relevant framework, the remediation owners assigned to each gap, and the target closure dates, because conformance to its required controls is the firmest signal of the unit's risk ahead of integration.
- C.The unit's overall risk exposure: which of its assets and data are most critical and sensitive, the threats it plausibly faces given its clinical trial data and external VPN links, the maturity of its existing controls, and the risk posture that results, so the risk program gains a structured baseline to monitor and prioritize against over time.
- D.The unit's threat environment: the adversaries likely to pursue unpublished clinical trial data, the motivations and techniques those actors typically rely on, the attack paths its external VPN links to research partners expose, and recent intrusion campaigns against biotech targets, because a detailed picture of who might attack and how is the substance of a risk profile.
Show the answer and reasoning
Correct answer: C
Developing a cybersecurity risk profile means characterizing the business unit's overall risk exposure by integrating several dimensions: which of its assets and data are most critical and how sensitive they are, the threats it plausibly faces in context (here, unpublished clinical trial data and site-to-site VPN links to external research organizations), the maturity of its existing controls, and the risk posture that results from combining those factors. That integrated characterization is what gives the parent company's risk program a structured baseline to monitor and prioritize the new unit over time, which is why the overall-risk-exposure option is correct. The technical-vulnerability option is wrong because a ranked inventory of scan and penetration-test findings is only one input to a profile: it captures current technical weaknesses but omits asset criticality, data sensitivity, control maturity, and the synthesized posture, making it a vulnerability register rather than a risk profile. The regulatory-conformance option is wrong because compliance is not the same as risk: a unit can conform fully to its applicable regulations and contract clauses while still carrying significant unaddressed exposure, so a compliance gap assessment characterizes conformance, not the unit's risk. The threat-environment option is wrong because profiling adversaries, their techniques, and likely attack paths produces a threat profile, which is an input to a risk profile rather than a substitute; on its own it omits the asset, control, and posture dimensions leadership needs to weigh and prioritize the unit's risk.
This question measures: T1079: Develop cybersecurity risk profiles
Sample question 3
You are the Cyber Risk Analyst at Meridian Health Partners, a regional healthcare payer. The CISO has asked you to build a FAIR-based loss-exceedance model for the scenario "ransomware disables claims-processing systems for 5 or more consecutive business days," to support a board decision on cyber insurance retention. You have gathered threat intelligence putting ransomware incidents against similar payers at roughly once every 8 years, along with claims-team estimates of downtime costs. The CFO, who has no security background, asks you to summarize the model before the board meeting. Which approach best reflects sound FAIR practice?
- A.Provide the CFO with the single most likely annual loss figure calculated from the median threat frequency and median loss magnitude, since a single number is easier for a non-technical board to act on than a probability distribution.
- B.Calculate threat event frequency from the exact historical ransomware base rate reported by a single vendor threat report, and present the expected loss to the nearest thousand dollars to demonstrate analytical rigor to the board.
- C.Present threat-event-frequency and loss-magnitude as calibrated ranges (e.g., 90% confidence intervals) derived from structured estimation, and show the resulting loss-exceedance curve so the board can see the probability of exceeding various loss thresholds, rather than a single number.
- D.Replace the numeric threat and loss estimates with a qualitative high, medium, or low risk rating for the scenario, since board members are generally more comfortable interpreting qualitative labels than they are interpreting probabilistic loss-exceedance curves.
Show the answer and reasoning
Correct answer: C
Building the model to FAIR standards means expressing both threat-event-frequency and loss-magnitude as calibrated ranges (for example, 90% confidence intervals) and presenting the resulting loss-exceedance curve, which is the only option that keeps the uncertainty visible and lets the board see the probability of exceeding different loss levels; that visibility is also what actually explains the model's assumptions to a non-technical stakeholder. Reporting only the single most-likely annual loss figure throws away the calibrated range and gives the board false confidence in one number. Using an uncalibrated single-vendor base rate and reporting the result to the nearest thousand dollars manufactures a look of precision the underlying estimate does not support. Replacing the numeric estimates with a qualitative high/medium/low label abandons quantification altogether, which defeats the purpose of building a FAIR model in the first place.
This question measures: RISKQ-T01: Construct a FAIR-based loss-exceedance model for a named risk scenario, including calibrated threat-event-frequency and loss-magnitude estimates, and explain its assumptions to a non-technical stakeholder
Job description templates
Three ready-to-edit drafts for hiring managers and recruiters: copy one, replace the bracketed lines, and post it. Responsibilities and requirements are drawn from the same NICE statements this role is measured against.
Statements use the official NICE Framework wording, which is published in English.
Cyber Risk Analyst: Junior
We are hiring a junior Cyber Risk Analyst. You tell the business what is risky, how much, and what to do about it. At this level you take on well-defined parts of the work, with senior colleagues to learn from, and grow into the rest.
[Company] provides [what you do]. The security function is [size and shape: e.g., a five-person team reporting to the CTO]. Replace this paragraph with your own.
Responsibilities
- Develop cybersecurity risk profiles
- Develop risk, compliance, and assurance monitoring strategies
- Establish stakeholder communication channels
- Develop a cybersecurity risk management plan
- Determine if authorization and assurance documents identify an acceptable level of risk for software applications, systems, and networks
- Develop organizational cybersecurity strategy
- Construct a FAIR-based loss-exceedance model for a named risk scenario, including calibrated threat-event-frequency and loss-magnitude estimates, and explain its assumptions to a non-technical stakeholder
- Translate a technical vulnerability or control gap into an annualized financial loss estimate suitable for an executive risk report
- Pair with senior colleagues and grow through structured feedback.
- Document what you do so the team learns with you.
Required knowledge
- Language processing tools and techniques
- Cybersecurity operation policies and procedures
- Cybersecurity practices in the acquisition process
- Intelligence fusion
- Cognitive biases
- Information privacy technologies
- Computer networking protocols
- Risk management processes
Skills
- Performing risk assessments
- Conducting test events
- Applying security controls
- Interfacing with customers
- Network systems management principles, models, methods (e.g., end-to-end systems performance monitoring), and tools
How to use this template
Copy the draft, replace every bracketed line, cut statements that do not apply to your opening, and add your compensation range and location policy. The statement lists come from the NIST NICE Framework v2.2.0, so candidates can be assessed against the same statements with Aramis:Insight.
Cyber Risk Analyst: Mid-level
We are hiring a mid-level Cyber Risk Analyst. You tell the business what is risky, how much, and what to do about it. You own this work day to day and work closely with the rest of the security team.
[Company] provides [what you do]. The security function is [size and shape: e.g., a five-person team reporting to the CTO]. Replace this paragraph with your own.
Responsibilities
- Develop cybersecurity risk profiles
- Develop risk, compliance, and assurance monitoring strategies
- Establish stakeholder communication channels
- Develop a cybersecurity risk management plan
- Determine if authorization and assurance documents identify an acceptable level of risk for software applications, systems, and networks
- Develop organizational cybersecurity strategy
- Construct a FAIR-based loss-exceedance model for a named risk scenario, including calibrated threat-event-frequency and loss-magnitude estimates, and explain its assumptions to a non-technical stakeholder
- Translate a technical vulnerability or control gap into an annualized financial loss estimate suitable for an executive risk report
- Build and maintain an enterprise cyber risk register with risk statements, ratings, ownership, and remediation timelines, and identify overdue items for escalation
- Prepare a board-level cyber risk report synthesizing quantified risk trends and a prioritized investment roadmap tied to risk reduction rather than control-count metrics
- Evaluate inherent versus residual risk for a system or business process and produce a supportable risk rating with documented rationale
- Prioritize a portfolio of identified risks by modeled financial impact and likelihood rather than by qualitative severity labels alone
Required knowledge
- Language processing tools and techniques
- Cybersecurity operation policies and procedures
- Cybersecurity practices in the acquisition process
- Intelligence fusion
- Cognitive biases
- Information privacy technologies
- Computer networking protocols
- Risk management processes
- Cybersecurity laws and regulations
- Cybersecurity policies and procedures
- Privacy laws and regulations
- Privacy policies and procedures
Skills
- Performing risk assessments
- Conducting test events
- Applying security controls
- Interfacing with customers
- Network systems management principles, models, methods (e.g., end-to-end systems performance monitoring), and tools
- Assessing security systems designs
- Applying secure coding techniques
- Performing root cause analysis
How to use this template
Copy the draft, replace every bracketed line, cut statements that do not apply to your opening, and add your compensation range and location policy. The statement lists come from the NIST NICE Framework v2.2.0, so candidates can be assessed against the same statements with Aramis:Insight.
Cyber Risk Analyst: Senior
We are hiring a senior Cyber Risk Analyst. You tell the business what is risky, how much, and what to do about it. You set the direction for this work, mentor the people who do it, and answer for its results.
[Company] provides [what you do]. The security function is [size and shape: e.g., a five-person team reporting to the CTO]. Replace this paragraph with your own.
Responsibilities
- Develop cybersecurity risk profiles
- Develop risk, compliance, and assurance monitoring strategies
- Establish stakeholder communication channels
- Develop a cybersecurity risk management plan
- Determine if authorization and assurance documents identify an acceptable level of risk for software applications, systems, and networks
- Develop organizational cybersecurity strategy
- Construct a FAIR-based loss-exceedance model for a named risk scenario, including calibrated threat-event-frequency and loss-magnitude estimates, and explain its assumptions to a non-technical stakeholder
- Translate a technical vulnerability or control gap into an annualized financial loss estimate suitable for an executive risk report
- Build and maintain an enterprise cyber risk register with risk statements, ratings, ownership, and remediation timelines, and identify overdue items for escalation
- Prepare a board-level cyber risk report synthesizing quantified risk trends and a prioritized investment roadmap tied to risk reduction rather than control-count metrics
- Evaluate inherent versus residual risk for a system or business process and produce a supportable risk rating with documented rationale
- Prioritize a portfolio of identified risks by modeled financial impact and likelihood rather than by qualitative severity labels alone
- Present risk-quantification results using Monte Carlo or loss-exceedance-curve outputs and defend the modeling approach under executive questioning
- Validate the output of an AI-assisted or automated risk-quantification tool against manual FAIR analysis and identify where model assumptions require adjustment
- Distinguish, in a written risk assessment, a control or compliance gap routed to control owners from a quantifiable enterprise risk requiring prioritization
- Serve on agency and interagency policy boards
- Mentor junior team members and review their work.
- Represent this function to leadership and to auditors or clients.
- Set standards, select tooling, and own the roadmap for this area.
Required knowledge
- Language processing tools and techniques
- Cybersecurity operation policies and procedures
- Cybersecurity practices in the acquisition process
- Intelligence fusion
- Cognitive biases
- Information privacy technologies
- Computer networking protocols
- Risk management processes
- Cybersecurity laws and regulations
- Cybersecurity policies and procedures
- Privacy laws and regulations
- Privacy policies and procedures
- Cybersecurity principles and practices
- Privacy principles and practices
Skills
- Performing risk assessments
- Conducting test events
- Applying security controls
- Interfacing with customers
- Network systems management principles, models, methods (e.g., end-to-end systems performance monitoring), and tools
- Assessing security systems designs
- Applying secure coding techniques
- Performing root cause analysis
- Performing network analysis on targets
- Performing target system analysis
How to use this template
Copy the draft, replace every bracketed line, cut statements that do not apply to your opening, and add your compensation range and location policy. The statement lists come from the NIST NICE Framework v2.2.0, so candidates can be assessed against the same statements with Aramis:Insight.
Related roles
Roles with similar work or at a similar career stage. Each has its own job description templates and a free assessment.