HITRUST CSF Assessment
Assess HITRUST Common Security Framework (CSF) certification readiness for "$ARGUMENTS". Determine assessment type, evaluate control domains, and identify the certification path.
Arguments. $ARGUMENTS may contain the project name and optional flags. Take the first token as <project> and treat --skip-checks as a flag; never include flags in file paths. All paths below use <project>. If --skip-checks is present, skip the prerequisite check and, before writing any artifact, append one line to .singularskills/log.jsonl: {"ts":"<ISO timestamp>","skill":"compliance-hitrust","workflow":"compliance","phase":1,"project":"<project>","event":"skipped","artifact":"01-assess/","note":"<reason or \"none given\">"}.
Prerequisites
Part of a workflow. This skill is phase 1 (Assess) of the GRC Lifecycle workflow (compliance); cross-domain workflows run it too. First check .singularskills/log.jsonl for an open run for this project: a run-started line with "project":"<project>" and no later run-finished line for the same workflow and project. If one exists, the conductor is running you: continue here. Otherwise, if the user asked to start, run, continue or resume a process or workflow rather than this one step, do not continue here: invoke the workflow skill with the workflow the user asked for, or compliance when they named none, followed by <project>; it runs this phase in order, asks before it writes and records the run. Otherwise continue here: a later phase runs on its own, behind its gate.
Run this skill's gate before writing: sh <this skill's folder>/scripts/gate.sh <project> <project root>, where <project root> is the folder that contains .singularskills/ (use . when you are already there). If it exits non-zero, stop and tell the user what it printed, unless --skip-checks was given (see Arguments). On a refusal, before you stop, append this line to .singularskills/log.jsonl (create the folder and file if missing): {"ts":"<ISO timestamp>","skill":"compliance-hitrust","workflow":"compliance","phase":1,"project":"<project>","event":"refused","artifact":"01-assess/","note":"<what the gate printed>"}. Once the gate has passed, or under --skip-checks once you have appended the skipped line, append this line before you start work: {"ts":"<ISO timestamp>","skill":"compliance-hitrust","workflow":"compliance","phase":1,"project":"<project>","event":"started","artifact":"01-assess/","note":""}.
Read .singularskills/compliance/<project>/00-scope.md. If this file does not exist, tell the user:
Phase 0 (Scope) has not been completed for "". Run /compliance-regulatory-landscape <project> first, or use --skip-checks to bypass.
Process
Read context files:
- Read
references/grc-lifecycle-guide.md for GRC methodology reference
- Read
references/assessment-template.md for output structure
- Read
.singularskills/compliance/<project>/00-scope.md for scope and control framework context
Assessment type determination:
- e1 (Essentials, 1-year) — assess suitability for low-risk organizations (44 controls)
- i1 (Implemented, 1-year) — assess suitability for moderate assurance needs (182 controls)
- r2 (Risk-based, 2-year) — assess suitability for high assurance requirements (full control set)
- Evaluate organization risk profile, regulatory requirements, and customer expectations
- Document recommended assessment type with rationale
Control domain assessment:
- Access Control — user access management, authentication, authorization, privileged access
- Human Resources Security — screening, terms of employment, security awareness, termination
- Risk Management — risk assessment methodology, risk treatment, risk acceptance criteria
- Security Policy — information security policies, management direction, review cycle
- Asset Management — asset inventory, acceptable use, information classification, media handling
- Communications and Operations Management — operational procedures, change management, capacity, malware, backup, network security, media handling, exchange of information, monitoring
- Information Systems Acquisition, Development, Maintenance — security requirements, secure development, test data, access control to source code
- Information Security Incident Management — incident response, reporting, evidence collection
- Business Continuity Management — BCM framework, BIA, BC plans, testing
- Compliance — legal requirements, security reviews, audit controls
- Privacy Practices — privacy program, notice, choice/consent, collection, use/retention/disposal
- Third-Party Assurance — vendor risk management, third-party agreements, monitoring
- Score each domain: 1 (policy), 2 (procedures), 3 (implemented), 4 (measured), 5 (managed)
Control mapping from existing frameworks:
- Map existing ISO 27001 controls to HITRUST requirements
- Map existing NIST CSF/800-53 controls to HITRUST requirements
- Map existing SOC 2 controls to HITRUST requirements
- Identify controls already satisfied by existing certifications
- Identify gaps requiring additional HITRUST-specific implementation
Certification path and timeline:
- Determine readiness timeline based on current maturity
- Identify external assessor (authorized HITRUST assessor) requirements
- Estimate assessment effort (internal preparation, external assessment)
- Estimate budget (HITRUST licensing, assessor fees, remediation costs)
- Define milestone timeline from current state to certification
Write the artifact to .singularskills/compliance/<project>/01-assess/hitrust.md following the assessment template structure with:
- Assessment Type Recommendation — e1/i1/r2 with rationale
- Control Domain Scoring — maturity score per domain
- Framework Mapping — existing controls mapped to HITRUST
- Gap Analysis — controls requiring new implementation
- Certification Path — timeline, assessor requirements, budget estimate
- Evidence Inventory — existing evidence and evidence gaps
- Remediation Priorities — ranked list of gaps to address
Output
The HITRUST CSF assessment written to .singularskills/compliance/<project>/01-assess/hitrust.md. Present a summary to the user highlighting:
- Recommended assessment type (e1/i1/r2)
- Overall control maturity score across domains
- Percentage of controls satisfied by existing framework certifications
- Top 3 gaps requiring remediation
- Estimated timeline to certification readiness
Record the run. After you have written the artifact, append this line to .singularskills/log.jsonl (the started line of Prerequisites, with "event":"finished"): {"ts":"<ISO timestamp>","skill":"compliance-hitrust","workflow":"compliance","phase":1,"project":"<project>","event":"finished","artifact":"01-assess/","note":""}.
Open the artifact with this frontmatter (agent is the agent you run in, or unknown; gate is passed when the gate ran clean and skipped under --skip-checks):
---
skill: compliance-hitrust
workflow: compliance
phase: 1
project: <project>
started: <ISO timestamp>
finished: <ISO timestamp>
agent: <the agent you run in, or "unknown">
gate: <passed|skipped>
---
End the artifact with ## Decisions and ## Open questions, in this shape:
## Decisions
- <what was chosen> — <why> — <what was rejected>
## Open questions
- <what the next phase or a reviewer must settle>
End the artifact with this paragraph, verbatim:
Not legal or audit advice. This artifact supports preparation for compliance work; certification, attestation and regulatory conclusions require a qualified auditor or counsel.
1---2name: compliance-hitrust3description: Assess HITRUST CSF certification readiness — choose the e1, i1 or r2 assessment, score control domains, map existing ISO 27001, NIST and SOC 2 controls, and estimate the certification path. Use when a healthcare customer demands HITRUST and the user wants to assess which assessment to pursue and how far their own controls are from it.4metadata:5 source: https://skillmd.com/skills/bromso/compliance-hitrust6 argument-hint: "[project] [--skip-checks]"7 workflow: compliance8 phase: 19 artifact: 01-assess/10---1112# HITRUST CSF Assessment1314Assess HITRUST Common Security Framework (CSF) certification readiness for "$ARGUMENTS". Determine assessment type, evaluate control domains, and identify the certification path.1516**Arguments.** `$ARGUMENTS` may contain the project name and optional flags. Take the first token as `<project>` and treat `--skip-checks` as a flag; never include flags in file paths. All paths below use `<project>`. If `--skip-checks` is present, skip the prerequisite check and, **before writing any artifact**, append one line to `.singularskills/log.jsonl`: `{"ts":"<ISO timestamp>","skill":"compliance-hitrust","workflow":"compliance","phase":1,"project":"<project>","event":"skipped","artifact":"01-assess/","note":"<reason or \"none given\">"}`.1718## Prerequisites1920**Part of a workflow.** This skill is phase 1 (Assess) of the GRC Lifecycle workflow (`compliance`); cross-domain workflows run it too. First check `.singularskills/log.jsonl` for an open run for this project: a `run-started` line with `"project":"<project>"` and no later `run-finished` line for the same `workflow` and `project`. If one exists, the conductor is running you: continue here. Otherwise, if the user asked to start, run, continue or resume a process or workflow rather than this one step, do not continue here: invoke the `workflow` skill with the workflow the user asked for, or `compliance` when they named none, followed by `<project>`; it runs this phase in order, asks before it writes and records the run. Otherwise continue here: a later phase runs on its own, behind its gate.2122Run this skill's gate before writing: `sh <this skill's folder>/scripts/gate.sh <project> <project root>`, where `<project root>` is the folder that contains `.singularskills/` (use `.` when you are already there). If it exits non-zero, stop and tell the user what it printed, unless `--skip-checks` was given (see Arguments). On a refusal, before you stop, append this line to `.singularskills/log.jsonl` (create the folder and file if missing): `{"ts":"<ISO timestamp>","skill":"compliance-hitrust","workflow":"compliance","phase":1,"project":"<project>","event":"refused","artifact":"01-assess/","note":"<what the gate printed>"}`. Once the gate has passed, or under `--skip-checks` once you have appended the `skipped` line, append this line before you start work: `{"ts":"<ISO timestamp>","skill":"compliance-hitrust","workflow":"compliance","phase":1,"project":"<project>","event":"started","artifact":"01-assess/","note":""}`.2324Read `.singularskills/compliance/<project>/00-scope.md`. If this file does not exist, tell the user:2526> Phase 0 (Scope) has not been completed for "<project>". Run `/compliance-regulatory-landscape <project>` first, or use `--skip-checks` to bypass.2728## Process29301. **Read context files:**31 - Read `references/grc-lifecycle-guide.md` for GRC methodology reference32 - Read `references/assessment-template.md` for output structure33 - Read `.singularskills/compliance/<project>/00-scope.md` for scope and control framework context34352. **Assessment type determination:**36 - **e1 (Essentials, 1-year)** — assess suitability for low-risk organizations (44 controls)37 - **i1 (Implemented, 1-year)** — assess suitability for moderate assurance needs (182 controls)38 - **r2 (Risk-based, 2-year)** — assess suitability for high assurance requirements (full control set)39 - Evaluate organization risk profile, regulatory requirements, and customer expectations40 - Document recommended assessment type with rationale41423. **Control domain assessment:**43 - **Access Control** — user access management, authentication, authorization, privileged access44 - **Human Resources Security** — screening, terms of employment, security awareness, termination45 - **Risk Management** — risk assessment methodology, risk treatment, risk acceptance criteria46 - **Security Policy** — information security policies, management direction, review cycle47 - **Asset Management** — asset inventory, acceptable use, information classification, media handling48 - **Communications and Operations Management** — operational procedures, change management, capacity, malware, backup, network security, media handling, exchange of information, monitoring49 - **Information Systems Acquisition, Development, Maintenance** — security requirements, secure development, test data, access control to source code50 - **Information Security Incident Management** — incident response, reporting, evidence collection51 - **Business Continuity Management** — BCM framework, BIA, BC plans, testing52 - **Compliance** — legal requirements, security reviews, audit controls53 - **Privacy Practices** — privacy program, notice, choice/consent, collection, use/retention/disposal54 - **Third-Party Assurance** — vendor risk management, third-party agreements, monitoring55 - Score each domain: 1 (policy), 2 (procedures), 3 (implemented), 4 (measured), 5 (managed)56574. **Control mapping from existing frameworks:**58 - Map existing ISO 27001 controls to HITRUST requirements59 - Map existing NIST CSF/800-53 controls to HITRUST requirements60 - Map existing SOC 2 controls to HITRUST requirements61 - Identify controls already satisfied by existing certifications62 - Identify gaps requiring additional HITRUST-specific implementation63645. **Certification path and timeline:**65 - Determine readiness timeline based on current maturity66 - Identify external assessor (authorized HITRUST assessor) requirements67 - Estimate assessment effort (internal preparation, external assessment)68 - Estimate budget (HITRUST licensing, assessor fees, remediation costs)69 - Define milestone timeline from current state to certification70716. **Write the artifact** to `.singularskills/compliance/<project>/01-assess/hitrust.md` following the assessment template structure with:72 - **Assessment Type Recommendation** — e1/i1/r2 with rationale73 - **Control Domain Scoring** — maturity score per domain74 - **Framework Mapping** — existing controls mapped to HITRUST75 - **Gap Analysis** — controls requiring new implementation76 - **Certification Path** — timeline, assessor requirements, budget estimate77 - **Evidence Inventory** — existing evidence and evidence gaps78 - **Remediation Priorities** — ranked list of gaps to address7980## Output8182The HITRUST CSF assessment written to `.singularskills/compliance/<project>/01-assess/hitrust.md`. Present a summary to the user highlighting:83- Recommended assessment type (e1/i1/r2)84- Overall control maturity score across domains85- Percentage of controls satisfied by existing framework certifications86- Top 3 gaps requiring remediation87- Estimated timeline to certification readiness8889**Record the run.** After you have written the artifact, append this line to `.singularskills/log.jsonl` (the `started` line of Prerequisites, with `"event":"finished"`): `{"ts":"<ISO timestamp>","skill":"compliance-hitrust","workflow":"compliance","phase":1,"project":"<project>","event":"finished","artifact":"01-assess/","note":""}`.9091Open the artifact with this frontmatter (`agent` is the agent you run in, or `unknown`; `gate` is `passed` when the gate ran clean and `skipped` under `--skip-checks`):9293```yaml94---95skill: compliance-hitrust96workflow: compliance97phase: 198project: <project>99started: <ISO timestamp>100finished: <ISO timestamp>101agent: <the agent you run in, or "unknown">102gate: <passed|skipped>103---104```105106End the artifact with `## Decisions` and `## Open questions`, in this shape:107108```markdown109## Decisions110- <what was chosen> — <why> — <what was rejected>111112## Open questions113- <what the next phase or a reviewer must settle>114```115116End the artifact with this paragraph, verbatim:117118> **Not legal or audit advice.** This artifact supports preparation for compliance work; certification, attestation and regulatory conclusions require a qualified auditor or counsel.