ServiceNow app · Blueshift Interactive

Dominion Shield reads every ACL, role, group and before-query rule on the tables you track, counts each active person once, and splits the answer into people with unrestricted access and people whose access depends on the record.

One count, every viewCards, the role grid, Explorer and detections all read the same tiers, so the numbers always agree.
Plain language firstEach cell says what it means in a sentence, with the quoted ACL condition one click away.
Change and driftA dot marks what moved since the last run, and detections separate upgrade changes from local edits.
Read-only by designIt never edits an ACL or a user. The only thing it writes is a review, routed to the right owner.
Heatmap

The whole table on one screen

Four cards answer "who can create, read, write and delete", split into unrestricted and conditional. Below them every role meets every operation, coloured by how access is decided.

dshield?id=dshield_home&table=sys_userTest-instance counts

Try it: select a big number to see how it adds up, or any cell to see who it covers and why.

Explorer

Every person behind the numbers

Reviewers see who sits inside each count, how they got the role, and what changed since the last run. Filter by operation, tier or role; the counts above still cover everyone.

dshield?id=dshield_explorer&table=sys_userSample people
PersonAccess viaCreateReadWriteDeleteSince last run
Select a person to evaluate them below.
Evaluate a user

Why can this person do that?

Before-query rules first, then every ACL the person's roles reach, in order. Compare two people side by side, or pick a record to see the answer for that record.

dshield?id=dshield_evaluateSample people

Security detections

Risks a security lead can act on

Read-only checks on the latest analysis and on recent ACL changes: broad exposure against the table's threshold, ACLs that changed in the drift window, and read access that list views can't filter.

dshield?id=dshield_detections&table=sys_userSample findings
Dominion Shield's model, not a live answer. Results come from the latest analysis of your ACLs. Scripts, conditions and rules Dominion Shield does not read can change what the platform actually allows.
Access reviews

A flag reaches the person who can answer it

Anyone with access to the portal can flag a cell. The review goes to the first match below, and the confirmation names who got it, so people can see routing working.

Dominion Shield > Access ReviewsSample owners
    Due in 10 daysCounted in working days when a business schedule is set in Settings.
    Reminders every 3 daysOverdue reviews email the assignee again until they're closed.
    Risk rules and exceptionsRules raise severity and can open reviews on their own. Approved exceptions silence a known risk until they expire.
    Settings

    Choose what it may track, and when it runs

    One Settings record holds the allowed tables, the weekly analysis time, retention and the fallback reviewer. A tracked table outside the allowed list can't be saved.

    Settings · Default
    Allowed tables
    Tables Dominion Shield may track. Leave empty to allow any table.
    Tracked tables

    Who uses it

    Three roles, three levels of detail

    Grant them through groups. Each role contains the one before it, and new viewers get a nine-step guided tour of the Heatmap on their first visit.

    Viewers

    x_blui2_dshield.viewer
    • Managers and service owners
    • Cards, role grid and tier counts
    • Flag a cell for review

    Reviewers

    x_blui2_dshield.reviewer
    • Role owners and access reviewers
    • Names in Explorer, deciding ACLs
    • Evaluate a user, work assigned reviews

    Admins

    x_blui2_dshield.admin
    • The team that runs the app
    • Settings, tracked tables, routing and risk rules
    • Security detections, approve explanations
    Straight answers

    What it won't claim

    An access tool is only useful if you can trust it. These are the places it tells you it doesn't know.

    Scripts aren't runA simple role check such as hasRole('itil, user_admin') is read. Any other script counts as conditional and shows its approved explanation, or says none exists yet.
    Not modeled means not modeledWhen a before-query rule or another mechanism also limits access, the cell says so instead of claiming Allowed.
    As of the last runNumbers come from the latest analysis, named on every page. Validation samples users and records and checks the model against the platform.
    Names stay privateViewers see counts. Names, paths and deciding ACLs need the reviewer role.

    See it on your own tables

    We'll point it at your most sensitive tables, run the first analysis, and walk through the results with your platform and security leads.

    Back to top
    Dominion Shield by Blueshift Interactive. Table counts come from a test instance; people, owners and findings on this page are sample data.