A risk assessment depends on what many people know, and they rarely know the same things. Engineers know
how the system fails, product owners know which losses matter, security people know which attacks are
current, and management knows what the organisation can bear. ArgueSecure gives them one shared graph to
add to, in a workshop room or over a few weeks, with comments and @mentions on the items they are
discussing.
- Start with a brainstorm. The first pass needs only titles: risks, ways they could happen, things that might help.
- Add numbers when you have them. No prior quantitative data is needed to begin. A value that is still missing is flagged, and the rest of the assessment works.
- Keep the reasoning. The claims and counter-claims, and the history of changes to them, stay in the assessment, so a reader can see how a conclusion was reached.
The idea comes from the 2016 paper behind the tool
(doi:10.1109/REW.2016.027). It starts from a
practical problem: in small companies and projects, a risk assessment is often skipped, done from a
checklist, or handed to an outside consultant. Checklists cover known risks but miss the ones that come
with new technology, and a consultant still needs the people who know the system and the people who hold
the budget. The paper argues for a participative session as a supplement to both, run by the project team
itself, since project teams are the most common participants in risk meetings and tend to prefer
qualitative methods.
The same reasoning shaped the online version. The people whose knowledge is needed are busy and rarely
free at the same time, so they should be able to add what they know from wherever they are, without
installing anything, while the link from each defence back to the risk it answers is kept.