Respuesta de referencia
Alternatively, a breach scenario can be explored conversationally. This more interactive approach can highlight how the candidate thinks, communicates, and collaborates. Interviewers can also tailor questions as they go (filling in information, digging deeper, etc.) to jibe with the candidate's experience level.
First though, it's important to establish a comfortable atmosphere, as a nervous person can be hard to read, says Dom Glavach, chief security officer and chief strategist at CyberSN, a career and staffing firm focused on cybersecurity.
That's why Glavach starts by asking about a well-publicized breach like the SolarWinds attack in terms of the indicators of compromise (IOC), lessons learned or the attack methodology used. “Even if they're not familiar with it, they can take a few seconds to do a search on IOC and SolarWinds,” he says. This reflects the on-the-job reality that security analysts shouldn't be judged on their immediate knowledge but on their ability to quickly assess risk and talk about remediations.
From there, Glavach moves to the scenario conversation, such as: Today's Monday. You're coming off a great weekend and see two odd login alerts the night before, from New York and San Francisco, within five minutes of each other, one of which was successful. You also detect a Cobalt Strike and beacons in the southern office. What do you need to do to triage this?
The rest of the conversation simulates what would occur in the security operations center (SOC) among colleagues, Glavach says, in terms of collaborating on ideas, sharing knowledge, assessing how dire the situation is and what should be done to remediate it. “I've heard answers that reveal the candidate is not as experienced as their resume led me to believe,” he says. “Resumes tell the story, but the person tells the novel.”