BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//Lucent Axis//SCOPE SOC 2 control calendar//EN
CALSCALE:GREGORIAN
METHOD:PUBLISH
X-WR-CALNAME:SCOPE SOC 2 controls
X-WR-CALDESC:The recurring SOC 2 controls from the control calendar. Planne
 d until the schedule starts.
BEGIN:VEVENT
UID:soc2-monthly@scope.lucent-axis
DTSTAMP:20261104T184827Z
DTSTART;VALUE=DATE:20261207
DTEND;VALUE=DATE:20261208
RRULE:FREQ=MONTHLY;BYDAY=1MO
SUMMARY:SOC 2: Monthly controls (6)
DESCRIPTION:Reminder: the window is open. Due by the 10th working day of th
 e month.\n\n- Review every pull request merged into lucent-axis/scope last
  month (gh pr list --state merged --search "merged:YYYY-MM-01..YYYY-MM-31"
 )\n  Who: Security owner\n  Audit evidence: The list\, with a line per Hig
 h-risk or emergency change\; a change the security owner made is reviewed 
 by the platform owner\n  SOC 2: CC8.1\, CC5.1\n- Dependabot and CI scan fi
 ndings: open criticals older than 7 days\, highs older than 30\n  Who: App
  owner\n  Audit evidence: Screenshot or export of the open alerts\, and th
 e fix or the risk-register entry\n  SOC 2: \n- Dashboard change log up to 
 date\n  Who: Platform owner\n  Audit evidence: The table in the change-man
 agement policy\n  SOC 2: \n- Security settings against the baseline: pytho
 n3 scripts/compliance/baseline_check.py --save\, then the dashboard rows r
 ead by hand into the same file\; every DRIFT either named to its readiness
  item or put back and logged\n  Who: Platform owner\n  Audit evidence: <da
 te>-security-baseline.md\n  SOC 2: CC7.1\n- Capacity: psql "$SUPABASE_DB_U
 RL" -f scripts/compliance/capacity.sql per client project (disk\, connecti
 ons\, cache\, largest tables\, long queries\; WATCH at 70%)\, and Supabase
  > Reports for CPU\; anything WATCH gets a plan\n  Who: Platform owner\n  
 Audit evidence: The script's output and a line\n  SOC 2: A1.1\n- Security 
 events: app logins flagged NEW or needing attention\, and every access cha
 nge of the last 35 days (psql "$SUPABASE_DB_URL" -f scripts/compliance/app
 _access.sql\, per client database)\, and sign-in failures in Supabase > Lo
 gs > Auth\n  Who: Platform owner\n  Audit evidence: The script's output an
 d a line on anything unexpected\n  SOC 2: CC7.2\n\nLeave a dated file unde
 r docs/compliance/evidence/<year>/ and a line in the evidence log.\nThe ca
 lendar: https://scope-safety-poc.vercel.app/hub/docs/compliance-control-ca
 lendar
URL:https://scope-safety-poc.vercel.app/hub/docs/compliance-control-calenda
 r
TRANSP:TRANSPARENT
BEGIN:VALARM
ACTION:DISPLAY
DESCRIPTION:SOC 2: Monthly controls (6)
TRIGGER;RELATED=START:PT9H
END:VALARM
END:VEVENT
BEGIN:VEVENT
UID:soc2-quarterly@scope.lucent-axis
DTSTAMP:20261104T184827Z
DTSTART;VALUE=DATE:20270118
DTEND;VALUE=DATE:20270119
RRULE:FREQ=YEARLY;BYMONTH=1,4,7,10;BYDAY=3MO
SUMMARY:SOC 2: Quarterly controls (5)
DESCRIPTION:Reminder: the window is open. Due by the month's last working d
 ay.\n\n- Access review of every account\n  Who: Security and platform owne
 rs\n  Audit evidence: scripts/compliance/access_review.sh output plus the 
 filled review table\, signed by both\n  SOC 2: \n- Security review meeting
 : this calendar's misses\, open risks\, incidents\, changes to the system\
 n  Who: Security and platform owners\n  Audit evidence: Minutes: who atten
 ded\, what was decided\, each miss and its fix\n  SOC 2: CC4.2\n- Risk reg
 ister reviewed\n  Who: Security owner\n  Audit evidence: The register's da
 te and changes\n  SOC 2: \n- Restore spot check: one table restored from b
 ackup into a throwaway project\n  Who: Platform owner\n  Audit evidence: T
 he restore test record\n  SOC 2: \n- Device check against the BYOD policy:
  Google Workspace endpoint verification where the edition reports it\, els
 e a dated screenshot per laptop (disk encryption\, screen lock\, OS versio
 n)\n  Who: Everyone\, collected by the security owner\n  Audit evidence: T
 he report or the screenshots\, per laptop\n  SOC 2: \n\nLeave a dated file
  under docs/compliance/evidence/<year>/ and a line in the evidence log.\nT
 he calendar: https://scope-safety-poc.vercel.app/hub/docs/compliance-contr
 ol-calendar
URL:https://scope-safety-poc.vercel.app/hub/docs/compliance-control-calenda
 r
TRANSP:TRANSPARENT
BEGIN:VALARM
ACTION:DISPLAY
DESCRIPTION:SOC 2: Quarterly controls (5)
TRIGGER;RELATED=START:PT9H
END:VALARM
END:VEVENT
BEGIN:VEVENT
UID:soc2-yearly-security-awareness-training-then-the-policies-re@scope.luce
 nt-axis
DTSTAMP:20261104T184827Z
DTSTART;VALUE=DATE:20261214
DTEND;VALUE=DATE:20261215
RRULE:FREQ=YEARLY;BYMONTH=12;BYDAY=2MO
SUMMARY:SOC 2: Security awareness training\, then the policies reviewed and
  re-signed by everyone
DESCRIPTION:Reminder: the window is open. Due by the month's last working d
 ay.\n\n- Security awareness training\, then the policies reviewed and re-s
 igned by everyone (one sitting)\n  Who: Security owner\, everyone\n  Audit
  evidence: Completion record and signed acknowledgement per person\n  SOC 
 2: \n\nLeave a dated file under docs/compliance/evidence/<year>/ and a lin
 e in the evidence log.\nThe calendar: https://scope-safety-poc.vercel.app/
 hub/docs/compliance-control-calendar
URL:https://scope-safety-poc.vercel.app/hub/docs/compliance-control-calenda
 r
TRANSP:TRANSPARENT
BEGIN:VALARM
ACTION:DISPLAY
DESCRIPTION:SOC 2: Security awareness training\, then the policies reviewed
  and re-signed by everyone
TRIGGER;RELATED=START:PT9H
END:VALARM
END:VEVENT
BEGIN:VEVENT
UID:soc2-yearly-risk-assessment-redone@scope.lucent-axis
DTSTAMP:20261104T184827Z
DTSTART;VALUE=DATE:20261214
DTEND;VALUE=DATE:20261215
RRULE:FREQ=YEARLY;BYMONTH=12;BYDAY=2MO
SUMMARY:SOC 2: Risk assessment redone
DESCRIPTION:Reminder: the window is open. Due by the month's last working d
 ay.\n\n- Risk assessment redone\n  Who: Security owner\n  Audit evidence: 
 The new register\n  SOC 2: \n\nLeave a dated file under docs/compliance/ev
 idence/<year>/ and a line in the evidence log.\nThe calendar: https://scop
 e-safety-poc.vercel.app/hub/docs/compliance-control-calendar
URL:https://scope-safety-poc.vercel.app/hub/docs/compliance-control-calenda
 r
TRANSP:TRANSPARENT
BEGIN:VALARM
ACTION:DISPLAY
DESCRIPTION:SOC 2: Risk assessment redone
TRIGGER;RELATED=START:PT9H
END:VALARM
END:VEVENT
BEGIN:VEVENT
UID:soc2-yearly-vendor-soc-2-reports-read-cuecs-checked@scope.lucent-axis
DTSTAMP:20261104T184827Z
DTSTART;VALUE=DATE:20261214
DTEND;VALUE=DATE:20261215
RRULE:FREQ=YEARLY;BYMONTH=12;BYDAY=2MO
SUMMARY:SOC 2: Vendor SOC 2 reports read\; CUECs checked
DESCRIPTION:Reminder: the window is open. Due by the month's last working d
 ay.\n\n- Vendor SOC 2 reports read\; CUECs checked\n  Who: Security owner\
 n  Audit evidence: Notes per vendor\n  SOC 2: \n\nLeave a dated file under
  docs/compliance/evidence/<year>/ and a line in the evidence log.\nThe cal
 endar: https://scope-safety-poc.vercel.app/hub/docs/compliance-control-cal
 endar
URL:https://scope-safety-poc.vercel.app/hub/docs/compliance-control-calenda
 r
TRANSP:TRANSPARENT
BEGIN:VALARM
ACTION:DISPLAY
DESCRIPTION:SOC 2: Vendor SOC 2 reports read\; CUECs checked
TRIGGER;RELATED=START:PT9H
END:VALARM
END:VEVENT
BEGIN:VEVENT
UID:soc2-yearly-secrets-and-keys-rotated@scope.lucent-axis
DTSTAMP:20261104T184827Z
DTSTART;VALUE=DATE:20261214
DTEND;VALUE=DATE:20261215
RRULE:FREQ=YEARLY;BYMONTH=12;BYDAY=2MO
SUMMARY:SOC 2: Secrets and keys rotated
DESCRIPTION:Reminder: the window is open. Due by the month's last working d
 ay.\n\n- Secrets and keys rotated: the database password\, Supabase secret
  keys\, Vercel and GitHub tokens\, the vault's production items\; the cred
 ential listing's "Last rotated" updated (onboarding-offboarding.md)\n  Who
 : Platform owner\n  Audit evidence: The credential listing with its new da
 tes\, and a line in the dashboard change log\n  SOC 2: \n\nLeave a dated f
 ile under docs/compliance/evidence/<year>/ and a line in the evidence log.
 \nThe calendar: https://scope-safety-poc.vercel.app/hub/docs/compliance-co
 ntrol-calendar
URL:https://scope-safety-poc.vercel.app/hub/docs/compliance-control-calenda
 r
TRANSP:TRANSPARENT
BEGIN:VALARM
ACTION:DISPLAY
DESCRIPTION:SOC 2: Secrets and keys rotated
TRIGGER;RELATED=START:PT9H
END:VALARM
END:VEVENT
BEGIN:VEVENT
UID:soc2-yearly-incident-response-tabletop@scope.lucent-axis
DTSTAMP:20261104T184827Z
DTSTART;VALUE=DATE:20270111
DTEND;VALUE=DATE:20270112
RRULE:FREQ=YEARLY;BYMONTH=1;BYDAY=2MO
SUMMARY:SOC 2: Incident response tabletop
DESCRIPTION:Reminder: the window is open. Due by the month's last working d
 ay.\n\n- Incident response tabletop (tabletop-exercises.md\, exercise 1)\n
   Who: Both owners\n  Audit evidence: Exercise record\n  SOC 2: \n\nLeave 
 a dated file under docs/compliance/evidence/<year>/ and a line in the evid
 ence log.\nThe calendar: https://scope-safety-poc.vercel.app/hub/docs/comp
 liance-control-calendar
URL:https://scope-safety-poc.vercel.app/hub/docs/compliance-control-calenda
 r
TRANSP:TRANSPARENT
BEGIN:VALARM
ACTION:DISPLAY
DESCRIPTION:SOC 2: Incident response tabletop
TRIGGER;RELATED=START:PT9H
END:VALARM
END:VEVENT
BEGIN:VEVENT
UID:soc2-yearly-full-timed-restore-test-against-rpo-and-rto-dr-t@scope.luce
 nt-axis
DTSTAMP:20261104T184827Z
DTSTART;VALUE=DATE:20270111
DTEND;VALUE=DATE:20270112
RRULE:FREQ=YEARLY;BYMONTH=1;BYDAY=2MO
SUMMARY:SOC 2: Full timed restore test against RPO and RTO\; DR tabletop
DESCRIPTION:Reminder: the window is open. Due by the month's last working d
 ay.\n\n- Full timed restore test against RPO and RTO\; DR tabletop (tablet
 op-exercises.md\, exercise 2)\n  Who: Platform owner\, both owners for the
  tabletop\n  Audit evidence: Restore test record\, exercise record\n  SOC 
 2: \n\nLeave a dated file under docs/compliance/evidence/<year>/ and a lin
 e in the evidence log.\nThe calendar: https://scope-safety-poc.vercel.app/
 hub/docs/compliance-control-calendar
URL:https://scope-safety-poc.vercel.app/hub/docs/compliance-control-calenda
 r
TRANSP:TRANSPARENT
BEGIN:VALARM
ACTION:DISPLAY
DESCRIPTION:SOC 2: Full timed restore test against RPO and RTO\; DR tableto
 p
TRIGGER;RELATED=START:PT9H
END:VALARM
END:VEVENT
BEGIN:VEVENT
UID:soc2-yearly-vulnerability-scan-or-pen-test@scope.lucent-axis
DTSTAMP:20261104T184827Z
DTSTART;VALUE=DATE:20270111
DTEND;VALUE=DATE:20270112
RRULE:FREQ=YEARLY;BYMONTH=1;BYDAY=2MO
SUMMARY:SOC 2: Vulnerability scan or pen test
DESCRIPTION:Reminder: the window is open. Due by the month's last working d
 ay.\n\n- Vulnerability scan or pen test\n  Who: Security owner\n  Audit ev
 idence: Report and fixes\n  SOC 2: \n\nLeave a dated file under docs/compl
 iance/evidence/<year>/ and a line in the evidence log.\nThe calendar: http
 s://scope-safety-poc.vercel.app/hub/docs/compliance-control-calendar
URL:https://scope-safety-poc.vercel.app/hub/docs/compliance-control-calenda
 r
TRANSP:TRANSPARENT
BEGIN:VALARM
ACTION:DISPLAY
DESCRIPTION:SOC 2: Vulnerability scan or pen test
TRIGGER;RELATED=START:PT9H
END:VALARM
END:VEVENT
END:VCALENDAR
