Clone Solutions
Template

Security Configuration Baseline

The agreed security settings for your Clone Enterprise organization, from SSO and roles to audit logs and skill change control, verified and signed by InfoSec.

What this is for

Before the first Clone does real work, InfoSec needs to know how the environment is configured and that it stays that way. This baseline records each control, the agreed setting, how it was verified and who owns it. It turns "is it secure?" into a checklist InfoSec can sign, and gives the team a reference to test against whenever settings change.

When to use it

Agree the baseline in the InfoSec kickoff. Verify it before InfoSec's own Clones go live in Week 4. Re-verify quarterly, after any major platform change, and before any audit evidence pack is assembled.

Who's involved

  • InfoSec lead: sets the required state and signs the baseline.
  • IT lead and org admin: apply identity and role settings.
  • GRC Specialist: facilitates and records evidence.
  • Implementation Engineer: applies Clone, skill and channel settings.
  • GRC Clone: drafts the baseline and runs the quarterly re-verification checklist.

How to fill it in

  1. Walk through each control area below with InfoSec. Agree the required setting, or mark it "Not applicable" with a reason.
  2. Apply the settings. Record who applied them and when.
  3. Verify each setting with evidence (a screenshot, an export or a test result). Link the evidence.
  4. Log any deviation as an exception with a compensating control, an owner and an expiry date.
  5. InfoSec signs. The baseline becomes the reference for the AI Risk Register and the Audit Evidence Pack.

The template

Control baseline

Status values: Agreed · Applied · Verified · Exception.

IDAreaControlRequired settingOwnerEvidenceStatus
ID-01IdentitySingle sign-onAll users sign in through the corporate IdPIT lead
ID-02IdentityMFAEnforced at the IdP for all users and adminsIT lead
ID-03IdentityProvisioning and deprovisioningJoiners added and leavers removed within the agreed windowIT lead
AC-01AccessOrg rolesRoles defined per the role matrix in the Connections & Permissions PlanOrg admin
AC-02AccessAdmin countNamed admins only, minimum needed, reviewed quarterlyInfoSec lead
AC-03AccessClone visibilityEach Clone visible only to the teams that use itOrg admin
CN-01ConnectionsApproved connections onlyEvery live connection matches an Approved row in the planImplementation Engineer
CN-02ConnectionsCredential storageSecrets stored in the platform's credential store, never in prompts or knowledgeImplementation Engineer
DA-01DataKnowledge sourcesOnly approved sources loaded; Restricted data excluded unless approvedBusiness owner
DA-02DataRetentionConversation and output retention set to the agreed periodInfoSec lead
DA-03DataResidencyData processed in the agreed regionInfoSec lead
AU-01AuditAudit loggingEnabled for all Clones, actions and admin changesGRC Specialist
AU-02AuditLog exportTamper-evident export to the client SIEM or archive at the agreed frequencyIT lead
AU-03AuditLog reviewExceptions and overrides reviewed at the weekly InfoSec syncInfoSec lead
AP-01ApprovalsApproval gatesActions at Execute with approval route to named approversBusiness owner
AP-02ApprovalsThresholdsExecute within limits thresholds documented in the Governance CharterBusiness owner
SK-01SkillsVersion pinningProduction Clones run pinned skill versionsImplementation Engineer
SK-02SkillsChange controlSkill upgrades tested against the test scenario pack before rolloutImplementation Engineer
CH-01ChannelsChannel allowlistClones reachable only on approved channels (e.g. Slack, Teams, email, phone)IT lead
CH-02ChannelsExternal exposureNo customer-facing channel without separate approvalInfoSec lead
IR-01IncidentKill switchNamed people can pause any Clone; testedInfoSec lead
IR-02IncidentIncident pathAI incidents follow the client incident process with a Clone contactInfoSec lead
ExampleAuditLog exportDaily export to SIEM, 13-month retentionIT leadExport job screenshot + first file hashVerified

Exceptions

IDControlDeviationReasonCompensating controlOwnerExpires
EX-01

Vendor assurance (reference)

ItemStatus
DPAProvided
BAAAvailable where applicable
GDPRIn place
SOC 2 Type I/IIIn progress
ISO 27001 and ISO 42001Targeted
Security whitepaperProvided

Mapping of these controls to SOC 2, HIPAA, NIST 800-53, CMMC or other frameworks is prepared for your own audits and is not legal advice.

Quarterly re-verification checklist

  • Admin list reviewed and reduced to minimum
  • All live connections match the plan
  • Skill versions in production match the approved list
  • Audit export running and complete for the quarter
  • Kill switch tested
  • Open exceptions reviewed; expired exceptions closed or renewed

Good looks like

  • Every row has evidence, not just "done." Auditors and your successors need proof.
  • Exceptions expire. An exception without an end date is a policy change nobody approved.
  • Kill switch tested, with the time it took recorded.
  • Baseline matches reality. Re-verification finds drift before an incident does.
  • Common mistake: writing the baseline from the vendor brochure. Agree the settings with InfoSec, then apply and verify them.

How Clone helps

The GRC Clone drafts the baseline from the pre-read and InfoSec's own policy, collects evidence links as settings are applied, and prompts owners for quarterly re-verification. The GRC Specialist runs the agreement session and reviews evidence. In the portal, this is the Security Configuration Baseline deliverable under Security & GRC; open exceptions and upcoming re-verification dates show on the InfoSec view.

Sign-off

RoleNameDateDecision
InfoSec leadApproved / Approved with exceptions
IT leadApplied
GRC SpecialistVerified