Security & GRC
InfoSec is the first department and a delivery partner all year. Covers identity, connections, the Governance Charter, AI use policy, risk register, autonomy promotions and audit evidence.
Owners
Clone Solutions: Security & GRC Specialist
Your side: InfoSec Lead
Supported by the GRC Clone
Year-1 outcomes
- SSO, role-based access and audit logging live by Day 14
- Every connection and autonomy promotion approved by InfoSec, with evidence
- Zero governance incidents above the agreed severity
- Audit Evidence Pack ready for the client's next audit by Day 245
- Client admins running governance operations by Day 300
Deliverables
- Vendor Security Package (DPA, BAA, whitepaper, compliance status)Day -7
- Connections & Permissions PlanDay 15
- Security Configuration BaselineDay 14
- Clone Governance CharterDay 21
- AI Risk RegisterDay 21
- AI Use PolicyDay 21
- Audit Evidence PackDay 245
Mobilize
Weeks −2 to 0
- Day -12Collect the client's security questionnaire and vendor onboarding formsStart vendor review in Mobilize so it does not become a Month 2 blocker.Security & GRC Specialist with InfoSec Lead
- Day -10Send the DPA, BAA if applicable, security whitepaper and compliance one-pagerState compliance status exactly: GDPR in place, BAAs available, SOC 2 Type I/II, ISO 27001 and ISO 42001 in progress.Security & GRC Specialist with InfoSec Lead
- Day -6Draft questionnaire answers with the GRC Clone and route gaps to Clone securityThe GRC Clone drafts from approved sources only. Anything new or ambiguous goes to a human reviewer before it is sent.Security & GRC Specialist with InfoSec Lead
- Day -5Confirm identity provider, group structure and 3 SSO test accountsLets SSO be configured in Week 1 instead of waiting on IT tickets.Implementation Engineer with IT Lead
Foundation
Days 1–30
- Day 3Record leadership's risk appetite for each autonomy levelWhich work leaders would accept at Execute with approval, and which must stay at Assist. Feeds the Governance Charter.Security & GRC Specialist with Steering Committee Member
- Day 4Run the InfoSec and IT kickoffSSO and identity, connection inventory, approval workflows, data classification and audit logs. Confirm InfoSec's own first Clones.Security & GRC Specialist with InfoSec Lead
- Day 6Configure SSO with the client's identity provider and test with 3 pilot usersTest sign-in, sign-out, group mapping and deprovisioning. Deprovisioning must remove Clone access within the agreed time.Implementation Engineer with IT Lead
- Day 7Inventory every system Clones may connect to, with data class and ownerInclude system owner, data classes held, available scopes and whether a service account or user-delegated access is needed.Implementation Engineer with IT Lead
- Day 8Define custom organization roles and map them to identity provider groupsSeparate who can use Clones, who can configure them, who can approve connections and who can see audit logs.Implementation Engineer with IT Lead
- Day 9Map the client's data classes to what Clones may read, write and retainRestricted data either stays out of knowledge or requires a named exception in the Governance Charter.Security & GRC Specialist with InfoSec Lead
- Day 10Set least-privilege scopes for each connection and name an approverRead-only by default. Write access only where a workflow needs it, tied to a named approver and a Clone in the charter.Security & GRC Specialist with InfoSec Lead
- Day 11Turn on audit logging and test tamper-evident export to the client's SIEMConfirm events, retention period and export format with InfoSec, then verify a test event end to end.Implementation Engineer with InfoSec Lead
- Day 12Configure approval routing in Slack or Teams for actions that need a named approverApprovers approve, edit or reject in one click. Test timeout behavior: an unanswered approval must never auto-approve.Implementation Engineer with IT Lead
- Day 14Publish the Security Configuration Baseline and get InfoSec sign-offEvery later change to SSO, roles, logging or approvals is checked against this baseline.Security & GRC Specialist with InfoSec Lead
- Day 15Get InfoSec approval on the Connections & Permissions PlanApproved connections can be turned on without a new review. Anything added later goes through the weekly InfoSec sync.Implementation Engineer with InfoSec Lead
- Day 16Run the governance design workshop with InfoSec, Legal and the sponsor's delegateApproval gates, escalation paths, what Clones may never do, risk tiers and human-in-the-loop thresholds.Security & GRC Specialist with InfoSec Lead
- Day 17Agree incident severity levels and the 'agreed severity' for Year-1 targetsDefine severities with examples, response times and who is told. The Year-1 target is zero incidents above the agreed level.Security & GRC Specialist with InfoSec Lead
- Day 18Draft the AI Use Policy: acceptable use, data handling, documenting AI involvementOne policy for Clones and third-party AI tools. Written for employees in plain language, with a one-page summary.Security & GRC Specialist with InfoSec Lead
- Day 19Seed the AI Risk Register with use-case risks, owners and review datesStart with the risks in this blueprint, then add use-case risks from the diagnostic. Every risk gets an owner on the client side.Security & GRC Specialist with InfoSec Lead
- Day 20Map EU AI Act, HIPAA and sector rules to the planned use casesFlags which use cases carry extra obligations. This is readiness mapping, not legal advice; the client's counsel reviews it.Security & GRC Specialist with InfoSec Lead
- Day 21Approve the Governance Charter, AI Use Policy and AI Risk RegisterInfoSec and the sponsor sign. The policy is published to staff with the sponsor's name on it.Security & GRC Specialist with InfoSec Lead
First departments live
Days 31–60
- Day 34Move the InfoSec sync to a standing weekly agendaNew connections, pending promotions, exceptions and overrides, risk register changes, upcoming go-lives.Security & GRC Specialist with InfoSec Lead
- Day 38Add Executive Clone entries to the Governance CharterRead-only mail and calendar, no external sends, no access to board or HR folders unless named.GRC Clone with InfoSec Lead
- Day 50Draft the autonomy promotion policy: evidence, sign-offs, demotion triggersEvidence thresholds per level, minimum days at level, who signs and what triggers an automatic step back down.Security & GRC Specialist with InfoSec Lead
- Day 56Approve the autonomy promotion policySigned by InfoSec, the sponsor and the first business owner. Added to the Governance Charter.Security & GRC Specialist with InfoSec Lead
- Day 57Promote the questionnaire Clone to Recommend using the first evidence packThe first promotion under the new policy, on InfoSec's own Clone. It tests the process before a business department depends on it.Security & GRC Specialist with InfoSec Lead
First results
Days 61–90
- Day 80Promote Department 1 workflows to Execute with approval with dual sign-offInfoSec and the business owner sign. Workflows that don't meet the evidence bar stay at Recommend.Security & GRC Specialist with Business Owner
- Day 82Review audit logs, exceptions and override rates with InfoSecSample 25 Clone actions per department: within charter, approved where required, logged correctly. Update the risk register from the findings.Security & GRC Specialist with InfoSec Lead
Department rollout
Days 91–180
- Day 100Run the first quarterly access review of Clone connections and remove unused scopesInfoSec's own Access Review Clone does the legwork. Unused scopes are removed, not left in place.Security & GRC Specialist with InfoSec Lead
- Day 135Promote Department 2 proven workflows to Execute with approvalSame evidence bar and dual sign-off as Department 1.Security & GRC Specialist with Business Owner
- Day 170Run a tabletop exercise: a Clone acts outside its limitsWalk detection, pause, notification and review. Fix any gap in the runbook within 2 weeks.Security & GRC Specialist with InfoSec Lead
Agentic organization
Days 181–270
- Day 185Identify workflows eligible for Execute within limits and draft their thresholdsThresholds are concrete: dollar amounts, record types, customer tiers. Anything outside escalates to a named person.Security & GRC Specialist with Business Owner
- Day 195Promote the first workflows to Execute within limits with escalation pathsInfoSec and business owner sign. Demotion triggers are live from day one.Security & GRC Specialist with InfoSec Lead
- Day 200Review customer-facing Clones for privacy, disclosure and consumer rulesIncludes call recording consent, SMS opt-in and accessibility. Not legal advice; client counsel signs off.Security & GRC Specialist with InfoSec Lead
- Day 205Confirm with the client's auditors which controls and evidence formats they expectAvoids building an evidence pack the auditor won't use.Security & GRC Specialist with InfoSec Lead
- Day 225Map Clone audit logs to the client's SOC 2, HIPAA, NIST 800-53 or CMMC controlsThe GRC Clone drafts the mapping; InfoSec confirms each control. Evidence supports the client's audits and is not a Clone certification.Security & GRC Specialist with InfoSec Lead
- Day 240Dry-run the Audit Evidence Pack with InfoSec as if the auditor asked todayPull 10 random control samples end to end. Fix gaps before the pack is called ready.Security & GRC Specialist with InfoSec Lead
- Day 245Promote the first Commander workflow to Orchestrate after its time at level 4Reviewed with InfoSec and the business owners of every department it touches.Security & GRC Specialist with InfoSec Lead
Self-sufficiency
Days 271–365
- Day 285Hand governance operations to client adminsConnection approvals, access reviews, charter updates and risk register reviews, with our specialist reviewing for one month.Security & GRC Specialist with Org Admin
- Day 300Have the CoE run an autonomy promotion review end to endWe observe and give feedback; we do not lead.Security & GRC Specialist with CoE Lead
- Day 325Refresh the Audit Evidence Pack for the next audit period and hand it to the CoEInclude how to regenerate the pack each period.Security & GRC Specialist with InfoSec Lead