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
- Walk through each control area below with InfoSec. Agree the required setting, or mark it "Not applicable" with a reason.
- Apply the settings. Record who applied them and when.
- Verify each setting with evidence (a screenshot, an export or a test result). Link the evidence.
- Log any deviation as an exception with a compensating control, an owner and an expiry date.
- 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.
| ID | Area | Control | Required setting | Owner | Evidence | Status |
|---|---|---|---|---|---|---|
| ID-01 | Identity | Single sign-on | All users sign in through the corporate IdP | IT lead | ||
| ID-02 | Identity | MFA | Enforced at the IdP for all users and admins | IT lead | ||
| ID-03 | Identity | Provisioning and deprovisioning | Joiners added and leavers removed within the agreed window | IT lead | ||
| AC-01 | Access | Org roles | Roles defined per the role matrix in the Connections & Permissions Plan | Org admin | ||
| AC-02 | Access | Admin count | Named admins only, minimum needed, reviewed quarterly | InfoSec lead | ||
| AC-03 | Access | Clone visibility | Each Clone visible only to the teams that use it | Org admin | ||
| CN-01 | Connections | Approved connections only | Every live connection matches an Approved row in the plan | Implementation Engineer | ||
| CN-02 | Connections | Credential storage | Secrets stored in the platform's credential store, never in prompts or knowledge | Implementation Engineer | ||
| DA-01 | Data | Knowledge sources | Only approved sources loaded; Restricted data excluded unless approved | Business owner | ||
| DA-02 | Data | Retention | Conversation and output retention set to the agreed period | InfoSec lead | ||
| DA-03 | Data | Residency | Data processed in the agreed region | InfoSec lead | ||
| AU-01 | Audit | Audit logging | Enabled for all Clones, actions and admin changes | GRC Specialist | ||
| AU-02 | Audit | Log export | Tamper-evident export to the client SIEM or archive at the agreed frequency | IT lead | ||
| AU-03 | Audit | Log review | Exceptions and overrides reviewed at the weekly InfoSec sync | InfoSec lead | ||
| AP-01 | Approvals | Approval gates | Actions at Execute with approval route to named approvers | Business owner | ||
| AP-02 | Approvals | Thresholds | Execute within limits thresholds documented in the Governance Charter | Business owner | ||
| SK-01 | Skills | Version pinning | Production Clones run pinned skill versions | Implementation Engineer | ||
| SK-02 | Skills | Change control | Skill upgrades tested against the test scenario pack before rollout | Implementation Engineer | ||
| CH-01 | Channels | Channel allowlist | Clones reachable only on approved channels (e.g. Slack, Teams, email, phone) | IT lead | ||
| CH-02 | Channels | External exposure | No customer-facing channel without separate approval | InfoSec lead | ||
| IR-01 | Incident | Kill switch | Named people can pause any Clone; tested | InfoSec lead | ||
| IR-02 | Incident | Incident path | AI incidents follow the client incident process with a Clone contact | InfoSec lead | ||
| Example | Audit | Log export | Daily export to SIEM, 13-month retention | IT lead | Export job screenshot + first file hash | Verified |
Exceptions
| ID | Control | Deviation | Reason | Compensating control | Owner | Expires |
|---|---|---|---|---|---|---|
| EX-01 |
Vendor assurance (reference)
| Item | Status |
|---|---|
| DPA | Provided |
| BAA | Available where applicable |
| GDPR | In place |
| SOC 2 Type I/II | In progress |
| ISO 27001 and ISO 42001 | Targeted |
| Security whitepaper | Provided |
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
| Role | Name | Date | Decision |
|---|---|---|---|
| InfoSec lead | Approved / Approved with exceptions | ||
| IT lead | Applied | ||
| GRC Specialist | Verified |