Triage is a reading and deciding job. You look at a list of findings, decide which matter, and send the real ones to the people who can fix them. A tablet suits that. It is large enough to read a finding properly and light enough to take to a meeting.
Safeguard is available on iPad and Samsung Galaxy Tab. For current downloads, see the download page.
What it is
The same Safeguard account and data, on a tablet screen. You can ask Griffin questions, look at findings, and follow up on notifications, all the things that work in the web app.
How to use it
- Install Safeguard from the download page guidance for your tablet and sign in.
- Start with a question: "What are the critical findings in this project, and which have a fix available?"
- Work down the list. For each one, decide: fix now, schedule, or accept with a reason.
- Send the ones that need work to the owning team.
A triage routine that fits a tablet
Keep it to three passes, so you do not get lost in a long list.
- Exploited first. Anything marked as known exploited gets decided today.
- Fixable next. If a fix exists, the decision is usually just who and when.
- Everything else last, and in bulk. Most of it is noise for your code paths.
Reachability helps with the third pass. Safeguard does reachability analysis, which checks whether your code calls the vulnerable function, so you can set aside findings that cannot be triggered in your project.
Try it yourself
Open a project and run the three passes against it with a timer. Aim for fifteen minutes. The demo below shows how fixes that are available right now stand out from the rest of the list.
Click through it at your own pace, or open it full screen.
Quick check
Which findings do you triage first?
Known exploited ones. Then findings with a fix available. The rest can be batched.
What does reachability analysis tell you?
Whether your code actually calls the vulnerable function, so you can deprioritize findings that cannot be reached.
