Security Analyst
You watch for trouble across the whole environment and dig into whatever looks off.
Competency areas
- Defensive Cybersecurity
- Systems Security Analysis
- Cybersecurity Policy and Planning
- Vulnerability Analysis
Aramis:Current Daily
A short reading list for a Security Analyst, under 30 minutes per edition.
2026-09-30. 27 minutes in total
Unauthenticated command injection on internet-facing mail servers: tracking CVE-2026-73570
Microsoft Threat Intelligence, 2026-09-30. Read, 25 min.
Why it matters for this role: Search archived logs beyond a 30-day hunting window on Zimbra hosts, as Microsoft notes the early exploitation it tracked is older than that window.
About the security content of iOS 26.7.1 and iPadOS 26.7.1
Apple, 2026-09-28. Read, 2 min.
Why it matters for this role: Start with the iPhones of people most likely to be singled out, given that the report Apple cites describes an attack on specific targeted individuals.
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
Bellwether Logistics deployed a cloud email security gateway to counter business email compromise, its highest-rated risk. Six months later, phishing-driven account compromises dropped from 40 per quarter to 3. All 3 remaining incidents were caught within an hour by the SOC's automated account-lockout playbook before any funds moved, and each involved one of a small group of executives who use a personal device that is not enrolled in the gateway. As the security analyst determining whether this deployment reduces the identified risk to an acceptable level, what should you conclude?
- A.Conclude the risk remains unacceptable because incidents still occurred, and replace the gateway with a different vendor product immediately.
- B.Conclude the risk is fully eliminated since incidents dropped sharply, and stop monitoring the gateway's effectiveness.
- C.Conclude the determination must wait until a full year of data is collected before evaluating the gateway's effectiveness.
- D.Conclude the residual risk is acceptable for now, since a compensating control catches remaining incidents before harm, and log the device gap.
Show the answer and reasoning
Correct answer: D
Option D is correct because acceptability of residual risk depends on whether remaining exposure is bounded by a working compensating control, which it is here: the lockout playbook intercepts every remaining incident before funds move, and the residual gap (unenrolled personal devices for a known small group) is narrow enough to track rather than escalate. Option A is wrong because it treats any nonzero incident count as unacceptable, ignoring that a functioning compensating control already neutralizes impact; replacing the vendor is not warranted by the evidence. Option B is wrong because 'fully eliminated' misreads a 92.5 percent reduction plus a working backstop as zero risk, and dropping monitoring would remove the very control the incidents show is doing the work. Option C is wrong because six months of consistent, favorable data already supports a determination, and deferring for a year leaves a known device gap undocumented and untracked in the meantime.
This question measures: T1176: Determine if cybersecurity-enabled products reduce identified risk to acceptable levels
Sample question 2
Harrier Underwriting's finance team has four staff, all cross trained to both create and approve wire transfers so the team can cover absences and vacations. There is no budget this year to add staff. Internal audit found two cases where the same employee created and approved the same wire transfer within minutes. The security analyst must recommend an access control addition that stops anyone from approving a transfer they created, while preserving every staff member's ability to perform either duty on other transfers. Which addition should the analyst recommend?
- A.Enforce static separation of duty by assigning the create and approve permissions to mutually exclusive finance roles.
- B.Add a dynamic separation of duty constraint: a transfer's creator cannot approve that same transfer but keeps both permissions.
- C.Apply attribute based rules that block approvals outside business hours and above each employee's individual transaction limit.
- D.Restructure approvals into a role hierarchy where a senior approver role inherits the junior creators' permissions downward.
Show the answer and reasoning
Correct answer: B
Dynamic separation of duty binds the conflict to the transaction instance: whoever created a given transfer is blocked from approving that one, while all four staff keep both permissions for every other transfer, satisfying both stated constraints. Static separation assigns the two permissions to mutually exclusive roles, which eliminates the cross coverage the four person team depends on. Attribute rules on hours and limits constrain when and how much, but the same person can still create and approve a single transfer inside those bounds. A role hierarchy changes who holds which permissions without any constraint tying creation and approval of the same transaction together.
This question measures: K0880: Knowledge of access control models and frameworks
Sample question 3
Fatima, a security analyst preparing a customer for a SOC 2 Type II examination, is reviewing the customer's identity and access management program. The customer's ERP system grants access purely through static job-title roles: every Accounts Payable Clerk receives identical permissions regardless of their device's patch status, working hours, or the sensitivity of the specific vendor records they touch. The examiner's draft finding requires that access decisions incorporate contextual risk factors, such as device compliance state and record sensitivity, without the business creating a new named role for every possible combination. Which remediation should Fatima recommend?
- A.Increase the granularity of the ERP's existing role hierarchy so that clerks are split into additional roles reflecting differences in device patch status, working hours, and vendor record sensitivity, then have identity management reassign each affected clerk to the role that matches their current profile.
- B.Adopt policy-based access controls that evaluate rules combining the clerk's attributes, the device's compliance posture, and the vendor record's sensitivity at the moment of each access request, granting or denying access dynamically from that real-time evaluation of context.
- C.Retire the standing role assignments entirely and require a manager-approved request form to be filed and reviewed before each vendor record is opened, so that every access decision becomes a one-off manual approval rather than a standing, rule-based grant.
- D.Layer conditional access policies onto the ERP so that every sign-in requires multi-factor authentication and is denied whenever the device fails its current patch-compliance check, bringing the device's real-time risk posture into each authentication decision for all clerks.
Show the answer and reasoning
Correct answer: B
Policy-based access control evaluates rules against the requester's attributes, the resource, and the environment, such as device compliance posture and record sensitivity, at the moment of the request, so it grants risk-appropriate access dynamically without a combinatorial explosion of named roles. Increasing role-hierarchy granularity is the role-explosion anti-pattern: it still relies on static roles decided in advance rather than evaluating context at request time, and it violates the constraint against creating a new named role for every combination. Retiring roles for manager-approved request forms replaces rules with one-off human judgment that does not systematically evaluate device posture or record sensitivity and does not scale. Layering conditional access with multi-factor authentication and device patch-compliance checks is tempting because it brings device state into the login decision, but it evaluates only the device at authentication and never weighs the specific vendor record's sensitivity at authorization, so the coarse role-driven authorization model the examiner flagged is unchanged.
This question measures: K0746: Knowledge of policy-based access controls
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.
Security Analyst: Junior
We are hiring a junior Security Analyst. You watch for trouble across the whole environment and dig into whatever looks off. 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
- Recommend vulnerability remediation strategies
- Determine if cybersecurity-enabled products reduce identified risk to acceptable levels
- Perform cyber defense trend analysis and reporting
- Serve on agency and interagency policy boards
- Recommend computing environment vulnerability corrections
- Determine the operational and safety impacts of cybersecurity lapses
- Review cyber defense service provider reporting structure
- Determine impact of software configurations
- Pair with senior colleagues and grow through structured feedback.
- Document what you do so the team learns with you.
Required knowledge
- Access control models and frameworks
- Policy-based access controls
- Programming language structures and logic
- Computer networking protocols
- Risk management processes
- Cybersecurity laws and regulations
- Cybersecurity policies and procedures
- Privacy laws and regulations
Skills
- Assessing security systems designs
- Performing packet-level analysis
- Developing policy plans
- Evaluating supplier trustworthiness
- Evaluating product trustworthiness
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.
Security Analyst: Mid-level
We are hiring a mid-level Security Analyst. You watch for trouble across the whole environment and dig into whatever looks off. 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
- Recommend vulnerability remediation strategies
- Determine if cybersecurity-enabled products reduce identified risk to acceptable levels
- Perform cyber defense trend analysis and reporting
- Serve on agency and interagency policy boards
- Recommend computing environment vulnerability corrections
- Determine the operational and safety impacts of cybersecurity lapses
- Review cyber defense service provider reporting structure
- Determine impact of software configurations
- Evaluate organizational cybersecurity policy regulatory compliance
- Evaluate organizational cybersecurity policy alignment with organizational directives
- Evaluate functional requirements
- Validate network alerts
Required knowledge
- Access control models and frameworks
- Policy-based access controls
- Programming language structures and logic
- 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
- Cybersecurity threats
Skills
- Assessing security systems designs
- Performing packet-level analysis
- Developing policy plans
- Evaluating supplier trustworthiness
- Evaluating product trustworthiness
- Identifying software communications vulnerabilities
- Developing user credential management systems
- Implementing user credential management systems
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.
Security Analyst: Senior
We are hiring a senior Security Analyst. You watch for trouble across the whole environment and dig into whatever looks off. 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
- Recommend vulnerability remediation strategies
- Determine if cybersecurity-enabled products reduce identified risk to acceptable levels
- Perform cyber defense trend analysis and reporting
- Serve on agency and interagency policy boards
- Recommend computing environment vulnerability corrections
- Determine the operational and safety impacts of cybersecurity lapses
- Review cyber defense service provider reporting structure
- Determine impact of software configurations
- Evaluate organizational cybersecurity policy regulatory compliance
- Evaluate organizational cybersecurity policy alignment with organizational directives
- Evaluate functional requirements
- Validate network alerts
- Determine if systems security operations and maintenance activities are property documented and updated
- Determine if security control technologies reduce identified risk to acceptable levels
- Establish stakeholder communication channels
- Maintain stakeholder communication channels
- 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
- Access control models and frameworks
- Policy-based access controls
- Programming language structures and logic
- 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
- Cybersecurity threats
- Cybersecurity vulnerabilities
- Cybersecurity threat characteristics
Skills
- Assessing security systems designs
- Performing packet-level analysis
- Developing policy plans
- Evaluating supplier trustworthiness
- Evaluating product trustworthiness
- Identifying software communications vulnerabilities
- Developing user credential management systems
- Implementing user credential management systems
- Implementing enterprise key escrow systems
- Recreating network topologies
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.