Skip to content

Main content

Biosecurity Supplied Permission Intersection Tool

Intersect explicit permission tokens and apply supplied denials without changing authorization.

Loading tool…

Description

Return requested permissions common to two lists and not denied.

Biosecurity administration records training assertions, custody, access purposes, inventories and document handling. Local counts, time checks and permission predicates describe supplied metadata; they do not authenticate people or items, enforce access or establish actual protective conditions.

Return requested permissions common to two lists and not denied.

When to use this tool

Use Biosecurity Supplied Permission Intersection when checking the stated benign biosecurity record, inventory, support or authorization convention.

How to use the tool and how it works

  1. Enter first, second, requested, deny. Follow any array-alignment requirements below. Use the units and conventions below.
  2. Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
  3. Read shared, allowed, deniedRequested. Use the output convention below.

Return requested permissions common to two lists and not denied. Deduplicate shared labels, allowed requested labels in the intersection outside deny, and deniedRequested labels absent from that result.1

Input fieldMeaning and unitsAccepted input
firstFirstRequired. Array of text; maximum UTF-16 length 8192; maximum items 256.
secondSecondRequired. Array of text; maximum UTF-16 length 8192; maximum items 256.
requestedRequestedRequired. Array of text; maximum UTF-16 length 8192; maximum items 256.
denyDenyRequired. Array of text; maximum UTF-16 length 8192; maximum items 256.
Output fieldInterpretationReturned shape
sharedSharedRequired. Array of text; maximum UTF-16 length 8192; maximum items 256.
allowedRequested labels in both permission sets and absent from deny; no actual access is granted.Required. Array of text; maximum UTF-16 length 8192; maximum items 256.
deniedRequestedDenied RequestedRequired. Array of text; maximum UTF-16 length 8192; maximum items 256.
json
{
  "input": {
    "first": [
      "read",
      "audit"
    ],
    "second": [
      "read",
      "audit"
    ],
    "requested": [
      "read",
      "audit",
      "write"
    ],
    "deny": [
      "audit"
    ]
  },
  "output": {
    "shared": [
      "read",
      "audit"
    ],
    "allowed": [
      "read"
    ],
    "deniedRequested": [
      "audit",
      "write"
    ]
  }
}

Limitations and assumptions

  • Deny takes precedence; no real policy, identity, authorization service or actual access control is invoked.
  • Inputs must satisfy both the field types and the cross-field conditions above. Invalid input causes an error; a successful false flag or documented placeholder is a different result.

Alternative or Complementary methods

Verify actual records, permissions and conditions through the responsible organization's procedures; use qualified risk assessment and appropriate professional oversight for practical decisions.

References

  1. Calculation and input contract: biosecurity/biosecurity-supplied-permission-intersection — tool.io

Similar or alternative tools