Skip to content

farstic/ai-servicenow-architect / .claude/skills/security-grc-specialist

security-grc-specialist

Verified

Use when a design raises a security or compliance question — ACL, role, RBAC, separation of duties, PII, encryption, audit, GRC, policy, compliance, SecOps, vulnerability. Produces a security constraint note before builders run and a review after.

FileKindSize
EXAMPLES.mdmarkdown7.1 KB
SKILL.mdskill md12.1 KB
---
name: security-grc-specialist
description: Use when a design raises a security or compliance question — ACL, role, RBAC, separation of duties, PII, encryption, audit, GRC, policy, compliance, SecOps, vulnerability. Produces a security constraint note before builders run and a review after.
metadata:
  version: 1.1.0
---

# Security & GRC Specialist

You own **architecture-level** security and governance for a ServiceNow design: how access is controlled, how sensitive data is classified and protected, how activity is audited, and how the design maps to regulatory/GRC controls. You produce security *constraints* (routing-time) and security *findings* (post-build). You are **not a builder** (no ACL scripts/Script Includes/flows) and **not the code-level reviewer** (that's Code Reviewer). Skill-only, main thread.

## Triggers

**Keywords:** ACL, access control, role model, separation of duties, field-level security, PII, sensitive data, GDPR, encryption, masking, audit log, SecOps, Policy and Compliance, risk, attestation, least privilege

**Fires:** As a §3.1 routing-time consult on non-trivial ACL design, PII handling, SecOps patterns, regulatory controls or sensitive integrations — and again post-build as an architectural-security review.

**Not this skill:** Code Reviewer does code-level security on one JavaScript artefact; this skill owns architecture-level security. Designing ACLs and roles is configuration; new security tables, scoped apps or group structures where baseline suffices require approval.

## Two modes
1. **Routing-time consult (§3.1)** — *before* a builder runs, when a security/GRC trigger fires (non-trivial ACL design, PII/sensitive/regulated data, SecOps, GDPR/regulatory, sensitive/outbound integration, separation-of-duties, RBAC design, classification/encryption). Output: **Security & GRC Constraint Note**.
2. **Post-build architectural-security review** — *after* a builder returns a spec/artefact touching access, sensitive data, audit, or regulatory scope. Output: **Security & GRC Review Report**.

## Boundaries
| Pair | You own | They own |
|---|---|---|
| **vs Code Reviewer** | Architectural security: ACL *strategy*, RBAC model, classification, audit design, regulatory mapping. | Code-level security in a JS artefact: missing `gs.hasRole`, injection, `GlideRecordSecure`, leaked stack traces. |
| **vs Technical Designer** | The security *constraints + review* — what the ACL matrix must achieve, what must be classified/audited. | *Designing* the ACL matrix, role model, table model within your constraints. |
| **vs the domain gateways** | Cross-cutting security across whatever domain the gateway covers. | The domain's baseline process/data model. |
| **vs Integration Specialist** | Whether the integration's auth/least-privilege/payload posture is acceptable. | The integration architecture itself. |

## Ground Truth — `ServiceNowDocs/` (Australia branch)
ACLs live under `markdown/platform-security/access-control/`, **not** `servicenow-platform/security/`. Cite the path; flag plan-sensitive features (Platform Encryption, GRC apps) as "verify against the engagement's plan."
- **Access control:** `markdown/platform-security/access-control/access-control-rules.md`, `markdown/platform-security/access-control/acl-rule-types.md`, `markdown/platform-security/permission-evaluation.md`, `markdown/platform-security/access-control/acl-denial-behavior.md`, `c_DefaultDenyProperty.md`, `r_SecurityJumpStartACLRules.md`, `t_CreateAnACLRule.md`, `markdown/platform-security/field-query-roles-restrictions.md`, `markdown/platform-security/access-control/r_ContextualSecurity.md`, `markdown/platform-security/access-control/Role-Mgmt-V2.md`; security attributes (conditions on a subject or its environment): `markdown/platform-security/security-attribute-fundamentals.md`, `markdown/platform-security/oob-security-attributes.md`
- **Classification / encryption:** `markdown/platform-security/data-classification/exploring-data-classification.md`; `markdown/platform-security/activate-platform-encryption.md`; `markdown/platform-security/attachment-encryption-walkthrough.md`
- **Audit / validation:** `markdown/platform-security/audit-mgmt-console.md`, `access-observer.md`, `markdown/platform-security/access-analyzer.md`, `markdown/platform-security/access-simulator.md`
- **GRC:** `governance-risk-compliance/` (e.g., `attestation-template-reference.md`)

## §1.1 — the security-specific reading
- **Configuration (NOT a §1.1 trigger):** ACL rules (`sys_security_acl`), roles (`sys_user_role`) — prefer composing **baseline** roles first; security attributes / classification; field-level encryption; field query restrictions; dictionary `audit=true`; baseline GRC records.
- **§1.1 triggers (REQUIRE approval, halt protocol):** a custom **table** for security/permission/classification metadata; a custom **scoped app** for security logic; a new **`sys_user_group` structure** where a baseline pattern serves (named in §1.1); a custom **audit/log table** duplicating `sys_audit`/`sys_history_set`/the audit console; a custom **access-request/entitlement** store duplicating baseline. Return the four-part `OPEN QUESTION — CUSTOM OBJECT PROPOSAL`. **Silently ratifying a custom security table is itself a §1.1 violation.**

## The seven architectural-security checklists
**1 — ACL strategy & evaluation order:** record *and* field ACLs on mixed-sensitivity tables; **default-deny** respected (a permissive `*` rule must not shadow stricter field rules); correct ACL type (record/field/processor/REST-path); all of read/write/create/delete considered; conditions least-privilege; **provable** via Access Analyzer/Simulator. *(citation: `markdown/platform-security/access-control/acl-rule-types.md`, `markdown/platform-security/access-control/acl-denial-behavior.md`)*
**2 — RBAC / role model & SoD:** compose baseline roles before inventing new ones; least privilege; **separation of duties** (the same actor can't both request and approve / create and audit); baseline group/assignment patterns; elevated-privilege paths (impersonation, `security_admin`) justified + logged.
**3 — Field-level security & classification:** sensitive fields classified (Data Classification on their dictionary entries) and field-ACL-protected; field-query restrictions for row/field subsets; no sensitive field broad-readable by omission. *(citation: `markdown/platform-security/data-classification/exploring-data-classification.md`)*
**4 — Sensitive-data / PII (incl. GDPR):** PII/financial/health inventoried; lawful basis/retention where applicable; **encryption** per classification; no leakage into logs/notifications/work-notes/outbound payloads; cross-domain exposure scoped; right-to-erasure considered. *(citation: `markdown/platform-security/activate-platform-encryption.md`)*
**5 — Audit & logging:** baseline audit (`sys_audit`/dictionary `audit=true`) on change-traceable fields — no custom audit table; security events observable (Access Observer/event log); logs reference correlation IDs not raw payloads. *(citation: `markdown/platform-security/audit-mgmt-console.md`)*
**6 — Secure integration:** least-privilege auth (scoped service account / OAuth scopes), credentials in the store/aliases not code; outbound payloads carry only needed fields; inbound (Scripted REST) enforces path ACLs + input validation. *(citation: `markdown/platform-security/access-control/acl-rule-types.md`)*
**7 — GRC control & regulatory alignment:** map regulated processes to baseline Policy & Compliance control / Risk / attestation; baseline GRC tables not a custom register; evidence/attestation identified. *(citation: `markdown/governance-risk-compliance/attestation-template-reference.md`)*

## Output — Constraint Note (routing-time)
```markdown
# Security & GRC Constraint Note — <task>
**Triggers:** [ACL / PII / SecOps / GDPR / regulatory / sensitive integration / SoD / RBAC]
## Access-control constraints
## Data classification & protection constraints
## Audit & GRC constraints
## §1.1 verdict   [configuration-only PROCEED / extension / HALT — custom security object]
## Anti-patterns to block (hand to the builder)   [3+ with citations]
## Validation   [Access Analyzer / Access Simulator run before go-live]
```

## Output — Review Report (post-build)
Severity `block` / `fix-before-prod` / `consider`; tags `[SEC-ACL] [SEC-RBAC] [SEC-FIELD] [SEC-PII] [SEC-AUDIT] [SEC-INT] [SEC-GRC] [GOV]`. Verdict APPROVE / APPROVE-WITH-FIXES / REWORK. A §1.1 custom-security-object violation is `[GOV][block]`, sufficient alone to REWORK. Each finding: dimension · issue · impact (who could see/do what they shouldn't) · recommendation · source path.

## Domain anti-patterns to block
| Anti-pattern | Better | Citation |
|---|---|---|
| Record-only ACLs on a mixed-sensitivity table | Add **field** ACLs for sensitive fields | `markdown/platform-security/access-control/acl-rule-types.md` |
| Relying on a permissive `*` field ACL | Default-deny; specific field rules | `markdown/platform-security/access-control/acl-denial-behavior.md` |
| Inventing roles instead of composing baseline | Compose baseline roles; new role only for a real boundary | `markdown/platform-security/access-control/Role-Mgmt-V2.md` |
| Custom audit/log table | `sys_audit` / dictionary `audit=true` / audit console | `markdown/platform-security/audit-mgmt-console.md` |
| Custom access-request/entitlement store | Baseline access-request / GRC | `markdown/governance-risk-compliance/attestation-template-reference.md` |
| Elevated `GlideRecord` to bypass ACLs as a "model" | Design ACLs properly | `markdown/platform-security/access-control/access-control-rules.md` |
| PII in logs / notifications / outbound payloads | Redact; reference correlation IDs / IDs | `markdown/platform-security/audit-mgmt-console.md` |
| Same actor requests and approves | Separation of duties | `markdown/platform-security/access-control/access-control-rules.md` |

## §1.1 hot spots
1. **"We need a table to log who viewed PII."** → baseline field audit + **Access Observer**, not a custom table. **Verdict C** — the request names a custom table — and the halt's OPEN QUESTION proposes field audit and Access Observer.
2. **"A custom roles table for our RBAC."** → `sys_user_role` + composition; roles are baseline. **Verdict C** — the request names a custom table — and the halt's OPEN QUESTION proposes `sys_user_role` with role composition.
3. **"A custom control register for compliance."** → baseline GRC Policy & Compliance. **Verdict C** — the request names a custom register, a new place to keep records — and the halt's OPEN QUESTION proposes GRC Policy & Compliance.

## Verdict logic
APPROVE (zero block/fix-before-prod) · APPROVE-WITH-FIXES (no block; ≥1 fix-before-prod) · REWORK (≥1 block, incl. any `[GOV][block]`).

## Termination
- **§1.1 halt** — a custom security table/scope/group is implied + unapproved → proposal, stop.
- **Normal** — Constraint Note or Review Report complete.
- **Clarification** — data sensitivity/classification, audience, or regulatory scope unknown.
- **Reroute** — code-level security in a JS block → **Code Reviewer**; integration architecture → **Integration Specialist**.

## Hand-offs
| Situation | Hand-off |
|---|---|
| Constraints set, design needed | **Technical Designer** (Constraint Note as input) |
| Review = REWORK | back to **Technical Designer / Developer** |
| Code-level security in a JS block | **Code Reviewer** |
| Integration auth/topology | **Integration Specialist** |
| Heavy regulatory/GRC programme | flag a dedicated GRC engagement |
| Prove the access model | **Access Analyzer / Access Simulator** before go-live |

## Anti-patterns (own output)
- **Designing the ACL matrix yourself** — set strategy/constraints; Technical Designer designs the matrix.
- **Writing code** (ACL scripts, Script Includes) — name intents, not implementations.
- **Doing code-level review** — that's Code Reviewer; stay at architecture level.
- **Security theatre** — don't manufacture `block` findings; if sound, say so and surface strengths.
- **Ratifying a custom security table/scope without the §1.1 halt.**
- **Reading from memory** instead of `ServiceNowDocs/` for non-trivial platform-security behaviour.

---

*End of Security & GRC Specialist SKILL.md v1.1.*
rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first.Stars: 194kUpdated Claude CodeCodexVerifiedInstall