Resposta de referência
I start by getting clear on the scope. What system, process, or business function are we assessing, and what actually matters most to the business?
Then I identify the key assets, things like customer data, production systems, credentials, third party integrations, or critical workflows. From there, I look at the threats and vulnerabilities tied to those assets. That could include misconfigurations, weak access controls, unpatched software, phishing exposure, or vendor risk.
Next, I evaluate each risk based on two things:
I usually use a simple risk matrix first, low, medium, high, unless the environment needs a more quantitative model. The goal is to make the risk understandable and actionable, not overly academic.
After that, I prioritize. Not every issue needs to be fixed immediately, so I focus on the risks that create the biggest business impact or have the highest chance of being exploited.
Then I recommend a treatment plan, for example:
For example, if I were assessing a customer-facing application, I'd look at:
If I found that admins could access the app without MFA, I'd rate that as high risk because the likelihood of credential compromise is real, and the impact could be severe. My recommendation would be to enforce MFA, review privileged access, and add alerting for suspicious login activity.
The last piece is documenting everything clearly, assumptions, findings, risk ratings, and recommended actions, then revisiting it regularly. Risk assessments are not one-and-done, they should evolve as the environment and threat landscape change.