Atlas Knowledge
Back to search
TechnologyUpdated 8/7/2025·3,960 views

Third-Party Software Security Review

Quick answer

New SaaS tools require IT Security review before purchase.

Full procedure

  1. 1Review the Third-Party Software Security Review standard on the department portal before you begin.
  2. 2Confirm you have the required access, PPE, or tooling for the task.
  3. 3New SaaS tools require IT Security review before purchase.
  4. 4Complete each step in sequence — do not skip or reorder.
  5. 5Record completion in the system of record (log, ticket, or checklist).
  6. 6Escalate any deviation from the standard through the escalation path.
  7. 7Debrief the team lead at handoff on anything unusual.

Common mistakes & exceptions

  • Skipping the WMS/system logging step — every action must have a system record.
  • Not photographing exceptions before escalating.
  • Assuming verbal approval is enough — always capture the ticket or form ID.

Escalation path & subject matter expert

Escalate to
Technology Shift Lead
Ext. 4130 · Slack #technology
Subject matter expert
Priya R. — Technology

Frequently asked questions

Required forms

  • Third-Party Software Security Review Log
    TEC-334

My private notes

saasvendorsecurity reviewprocurementthird-partysoftwaresecurityreviewtechnologyproceduresopatlas

Revision history

  1. 2025-08-07
    Version 3.1 republished by Tobias Grant.
  2. 2026-05-10
    Reviewed for annual compliance.
  3. 2024-11-04
    Initial publication.
Was this helpful?
Your feedback improves the knowledge base.