Move Vanta compliance responsibilities from Finance to IT (#42074)

## Summary - Moved the "Monitor compliance tests" (Vanta) responsibility section from the Finance department handbook page to the IT department handbook page. - Moved the corresponding "Vanta check" ritual entry from `finance.rituals.yml` to `it.rituals.yml`, updating the `moreInfoUrl` to point to `handbook/it#monitor-compliance-tests` and the label to `:help-it`. - Updated the GitHub label reference in the responsibility text from `:help-finance` to `:help-it`. - Added a backward-compatible stub on the Finance page redirecting old links to the new IT location. ## Changes | File | Change | |------|--------| | `handbook/finance/README.md` | Removed "Monitor compliance tests" section; added redirect stub | | `handbook/it/README.md` | Added "Monitor compliance tests" section under Responsibilities | | `handbook/finance/finance.rituals.yml` | Removed "Vanta check" ritual entry | | `handbook/it/it.rituals.yml` | Added "Vanta check" ritual entry with updated URL and label | --- Built for [Isabell Reedy](https://fleetdm.slack.com/archives/D0AEGJCGJR0/p1773933615134779) by [Kilo for Slack](https://kilo.ai/features/slack-integration) --------- Co-authored-by: kiloconnect[bot] <240665456+kiloconnect[bot]@users.noreply.github.com> Co-authored-by: Isabell Reedy <113355639+ireedy@users.noreply.github.com>
2026-03-19 15:21:43 -05:00
parent 99f8639484
commit 2a85a5f5b6
4 changed files with 26 additions and 30 deletions
@@ -480,16 +480,6 @@ When an agreement is routed to the [CFO](https://fleetdm.com/handbook/finance#te
 2. The CFO will comment in the issue once they've signed the agreement and assign the issue to [Deal Desk](https://fleetdm.com/handbook/finance#team) to confirm a signed copy of the agreement is correctly stored in Google Drive. Then the issue can be closed.  


-### Monitor compliance tests
-
-1. Every Monday, log in to Vanta and create GitHub issues for any tests that are due or need remediation in the next 3 weeks.    
-2. To do this, access "Tests" on the left side menu.  This will provide a status report of the tests, when they are due, and who the DRI is.  
-3. Click on a test, then click on "Tasks".  
-4. Click on "Create task." Then, "Create GitHub issue."
-5. This will bring you to a screen where you can select the appropriate DRIs and GitHub labels (multiple, if necessary, but always include the ":help-finance" label). Vanta will autopopulate the issue with a brief description of the test due and what needs to be remediated. You can manually add details if necessary.
-6. Follow up with the DRI of each issue daily until it's resolved. As needed, loop in their manager, the [Head of People](https://fleetdm.com/handbook/people#team),Fleet's CTO, or the Head of IT. If the test is within 3 days of being overdue, DM the fleetie and their manager, asking to have the issue prioritized and completed before the due date.
-
-
 ### Check GitHub terms

 Go to [GitHub's terms of services](https://docs.github.com/en/free-pro-team@latest/github/site-policy/github-terms-of-service) and search “inbound=outbound” to find the clause, if still there as is, paste a screenshot into the table in this [document](https://docs.google.com/document/d/101rcp9v3Zdml4YolGRmqYS5ruAKzQvXLOTHLXCavPuE/edit#heading=h.xu6qsi0wrns). If the clause has changed, contact Mike M. and let him know.
@@ -555,6 +545,9 @@ The following table lists this department's rituals, frequency, and Directly Res
 #### Stubs
 The following stubs are included only to make links backward compatible.

+##### Monitor compliance tests
+Please see [handbook/it#monitor-compliance-tests](https://fleetdm.com/handbook/it#monitor-compliance-tests)
+
 ### Run payroll
 Please see [handbook/people#run-payroll](https://fleetdm.com/handbook/people#run-payroll)

@@ -22,15 +22,6 @@
  autoIssue:
    labels: [":help-finance"]
    repo: "confidential"
- task: "Vanta check"
-  startedOn: "2025-06-09"
-  frequency: "Weekly"
-  description: "Every Monday, log in to Vanta and create GitHub issues for any tests that are due or need remediation in the next 3 weeks."
-  moreInfoUrl: "https://fleetdm.com/handbook/finance#monitor-compliance-tests"
-  dri: "rfoo2015"
-  autoIssue:
-    labels: [":help-finance"]
-    repo: "confidential"
 - task: "Key review prep"
  startedOn: "2024-02-14"
  frequency: "Triweekly"
@@ -79,9 +79,14 @@ Once the department approves inventory to be shipped from Fleet IT, follow these
 7. Add a comment to the equipment request issue, at-mentioning the requestor with the FedEx tracking info and close the issue.


+### Monitor compliance tests

-   
-
+1. Every Monday, log in to Vanta and create GitHub issues for any tests that are due or need remediation in the next 3 weeks.    
+2. To do this, access "Tests" on the left side menu.  This will provide a status report of the tests, when they are due, and who the DRI is.  
+3. Click on a test, then click on "Tasks".  
+4. Click on "Create task." Then, "Create GitHub issue."
+5. This will bring you to a screen where you can select the appropriate DRIs and GitHub labels (multiple, if necessary, but always include the ":help-it" label). Vanta will autopopulate the issue with a brief description of the test due and what needs to be remediated. You can manually add details if necessary.
+6. Follow up with the DRI of each issue daily until it's resolved. As needed, loop in their manager, the [Head of People](https://fleetdm.com/handbook/people#team), Fleet's CTO, or the Head of IT. If the test is within 3 days of being overdue, DM the fleetie and their manager, asking to have the issue prioritized and completed before the due date.



@@ -1,20 +1,27 @@
 # https://github.com/fleetdm/fleet/pull/13084
-
-  task: "Prioritize for next sprint" # Title that will actually show in rituals table
+- task: "Prioritize for next sprint" # Title that will actually show in rituals table
  startedOn: "2023-08-09" # Needs to align with frequency e.g. if frequency is every thrid Thursday startedOn === any third thursday
  frequency: "Triweekly" # must be supported by https://github.com/fleetdm/fleet/blob/dbbb501358e226fa3fdf48865175efe3334c826c/website/scripts/build-static-content.js
-  description: "Using your departmental kanban board, prioritize and finalize next sprint's goals for your team by draging the appropriate issues to the top of the 'Planned' column and archive everything in the 'Done' column." 
+  description: "Using your departmental kanban board, prioritize and finalize next sprint's goals for your team by draging the appropriate issues to the top of the 'Planned' column and archive everything in the 'Done' column."
  moreInfoUrl: "https://fleetdm.com/handbook/company/why-this-way#why-make-work-visible" #URL used to highlight "description:" test in table
  dri: "allenhouchins" # DRI for ritual (assignee if autoIssue) (TODO display GitHub proflie pic instead of name or title)
-  autoIssue:   
-    labels: [ ":help-solutions-consulting" ]
+  autoIssue:
+    labels: [":help-solutions-consulting"]
    repo: "confidential"
-
-  task: "Review active eval instances"
+- task: "Vanta check"
+  startedOn: "2025-06-09"
+  frequency: "Weekly"
+  description: "Every Monday, log in to Vanta and create GitHub issues for any tests that are due or need remediation in the next 3 weeks."
+  moreInfoUrl: "https://fleetdm.com/handbook/it#monitor-compliance-tests"
+  dri: "lppepper2"
+  autoIssue:
+    labels: [":help-it"]
+    repo: "confidential"
+- task: "Review active eval instances"
  startedOn: "2025-08-25"
  frequency: "Monthly"
  description: "Review [list of active instances](https://github.com/fleetdm/confidential/tree/main/infrastructure/cloud) to see what can be shutdown and deleted."
  dri: "allenhouchins"
-  autoIssue:   
-    labels: [ ":help-solutions-consulting" ]
+  autoIssue:
+    labels: [":help-solutions-consulting"]
    repo: "confidential"