Show each team only the risk it owns
Assign risks to teams so members focus on their own area of responsibility, while everyone else is kept out on a need-to-know basis.
Why it matters
Not everyone should see every risk
Risk records often hold sensitive detail, and the physical security team has no need to see the Unix team’s exposures, or the other way around.
Without separation, every risk is visible to everyone, which is both a distraction from the work that is actually theirs and a need-to-know problem you would rather not have.
What it does
Show each team only what it owns
The Team-Based Separation Extra restricts a risk to the team, or teams, it is assigned to, so members focus on their own area while everyone else is kept out by default.
- Team-scoped access. A risk is visible only to the team, or teams, it is assigned to.
- Focus and collaboration. Members work the risks that are actually theirs.
- Need-to-know by default. Separate, say, your Unix team from physical security.
How it works
Up and running in three steps
Assign the risk
Attach each risk to the team, or teams, that own it.
Scope the access
Members of that team can see and work it; others cannot.
Keep it need-to-know
Sensitive risk stays with the people who should have it.
Keep risk on a need-to-know basis
Start a free trial or book a demo to see team separation live.
Start a free trial