Vendor reports re-measured against the current policy and tier.
What it solves: Vendor security packages in Box, tiers and spend in Attio and an age-limit policy in Drive come together in one Kylon room. Agents measure every report against its limit and re-measure all vendors when a limit changes, and the risk lead approves each result.
How it runs
- First disposition Each vendor’s newest report is measured against its tier limit and marked cleared, conditional or blocked, with a reason and the days over the limit Who decides: The risk lead approves before Attio is updated
- Review batches Blocked and conditional vendors are grouped into reviewer batches in order of annual spend from Attio Who decides: The risk lead assigns each batch to a reviewer
- Notice list audit The draft list of vendors to notify is checked against the approved dispositions, in both directions Who decides: The risk lead corrects and approves the list
- Limit revision Every vendor is re-measured under the new table, and any change in reason or days over the limit is recorded as a revision Who decides: Security confirms how the new limit reads
- Findings batch New penetration test findings are attached to their vendors and those dispositions re-checked Who decides: The security reviewer decides whether each finding blocks
- Reclassification A tier change on one vendor is applied, then the whole blocked list is re-confirmed in batch order Who decides: The risk lead approves the resulting order
- Closeout Four closeout records are written from current Attio data, one per vendor tier, each with the same fixed fields Who decides: The risk lead signs each record
Tools it connects
- Attio: Holds each vendor’s record, tier, business owner and annual spend, and receives every approved disposition.
- Box: Holds the security packages: SOC reports, bridge letters, penetration test summaries and questionnaires.
- Google Drive: Keeps the assessment policy, the age-limit table and the draft notice list.
- Outlook (optional): Is where vendors send updated reports, and where notices go out once a person sends the draft.
- Slack (optional): Is where business owners ask when their vendor will clear, and Ryan collects those questions in the assessment thread.
Set-up prompt
Paste this into Kylon, or start it in one click below.
Set up our vendor security assessment desk in this Room. Take it one step at a time and wait for my OK before you move on.
1. Connect Attio, Box and Google Drive first, since the first run needs them. Tell me which ones still need connecting. Outlook and Slack can wait until a step uses them.
2. Ask me who works this desk: the third-party risk lead, the security reviewers who work through each batch, and the business owners who hold the vendor relationships. Help me invite them to this Room.
3. Build a Vendor Assessments App with Vendor, Tier, Report age and Status, one record per vendor. Pull each vendor's tier, business owner and annual spend from Attio, and read the security packages from the Box folders.
4. Measure each vendor's newest report against the tier limit in the Google Drive policy table. Propose a disposition, a reason and the days over the limit for every vendor. Show the ones that land blocked or conditional, grouped into review batches in order of annual spend from Attio only. Flag any report found in the wrong Box folder.
5. Draft vendor notices in the risk lead's Outlook and hold every Attio update and every notice until the risk lead approves. When a limit or tier changes, re-measure every vendor, record any change in reason or days as a revision, and list old and new figures side by side for the risk lead to approve in one pass.
6. Write the rule order and who approves what into this Room's guideline, so every cycle follows it.
7. After one clean cycle, offer to turn the re-measure step into an Automation.
Start with step 1. Once the tools are connected, or I say the rest can wait, ask me for our rules one at a time.