Skip to main content
HITRUST

HITRUST MyCSF Explained: A Guide for First-Timers

Published
Last updated
HITRUST
A glowing assessment dashboard with checklist rows and maturity bars, connected to icons for the internal team, a consultant, an assessor and an evidence upload, representing HITRUST MyCSF

If you are starting your first HITRUST assessment, you will spend a lot of time in MyCSF. It is where your assessment is scoped, where your evidence lives and where your assessor does their work. This guide explains what MyCSF is, who does what inside it, how scoping and scoring work in general terms, and how to keep it organized. For hands-on help, see our HITRUST consulting page.

We keep the scoring explanation general on purpose. HITRUST defines the scoring rules, and your Authorized External Assessor explains how they apply to your assessment.

What is HITRUST MyCSF?

MyCSF is HITRUST's online platform for running HITRUST assessments. You use it to create and scope your assessment, see the requirements that apply to you, record how each one is met, upload evidence, request inheritance from participating providers and work with your assessor. The validated assessment is submitted to HITRUST through MyCSF for review before certification.

In practice, MyCSF is the single place where everyone involved in your assessment works from the same list of requirements. That is what makes it useful, and also why a messy MyCSF makes an assessment harder.

Who does what in MyCSF?

Four parties are usually involved: your own team, which owns the controls and evidence; your consultant, who helps with scoping, readiness and organizing evidence; your HITRUST Authorized External Assessor, who tests your controls and submits the assessment; and HITRUST, which reviews the submission and decides on certification.

RoleWhat they do in MyCSFWho it is for CyberWave GRC clients
Your teamOwns the controls, answers for each requirement and uploads evidenceYour security, engineering, IT and HR owners
ConsultantScoping, gap assessment, remediation guidance, evidence organization and inheritance mappingCyberWave GRC
Authorized External AssessorTests controls and evidence, records results and submits the validated assessmentHuduku AI, our independent partner
HITRUSTQuality assurance review and the certification decisionHITRUST

Keeping these roles separate matters. Your consultant prepares you; the assessor tests you independently; HITRUST certifies. CyberWave GRC never issues HITRUST certifications.

How is a HITRUST assessment scoped in MyCSF?

Scoping in MyCSF starts with choosing the assessment type, e1, i1 or r2, and defining the systems, locations and services in scope. For the r2, HITRUST also uses risk factors, such as organization size, data volume, systems and regulatory scope, to tailor which requirements apply. A tight, accurate scope keeps the work manageable.

Questions to settle before you build the assessment:

  • Which assessment? Ask your customer what they will accept. Our free HITRUST assessment chooser can help.
  • Which systems? List the applications, infrastructure and data stores that handle the data your customer cares about.
  • Which locations and teams? Include offices and remote teams that support in-scope systems.
  • Which cloud services? Record the provider services your systems run on, so inheritance can be mapped.
  • What is out of scope? Write down what you are excluding and why.

The e1 covers 44 foundational controls and the i1 about 182 control requirements. The r2 is tailored, so its size depends on your scoping answers.

How does scoring work in MyCSF?

HITRUST scores each requirement against defined maturity levels, which look at whether a control is documented, how it is carried out and whether it is actually implemented. The r2 looks more deeply at maturity than the e1 and i1. HITRUST sets the scoring model, and your assessor explains how it applies to your assessment.

What this means in practice:

  • A written policy is not enough on its own. Assessors look for evidence that the control is in place and working.
  • Consistency counts. A control that works in one team but not another will score lower.
  • Evidence drives the score. Clear, dated evidence that matches the requirement makes scoring straightforward.

If you are unsure how a requirement will be scored, ask your assessor before you upload evidence, not after.

What evidence goes into MyCSF?

Evidence in MyCSF is whatever shows a requirement is met: policies and procedures, configuration screenshots, system reports, logs, access reviews, training records, risk assessments, vendor reviews and test results. Each item should be clearly named, dated and linked to the requirement it supports, so your assessor can test it without asking where it came from.

A few habits make evidence much easier to work with:

  1. Name files consistently, with the requirement, the system and the date.
  2. Show the period covered. Assessors need to see that controls operate over time, not just on one day.
  3. Redact carefully. Remove sensitive data you don't need to share, without hiding what proves the control.
  4. Separate your side from inherited parts. For shared controls, upload evidence of your responsibilities.
  5. Keep a source of truth. Agree where evidence is produced and who uploads it, so nothing is duplicated.

How does inheritance work in MyCSF?

Inheritance is requested inside MyCSF. If your systems run on cloud providers that take part in HITRUST's Shared Responsibility and Inheritance Program, you can request to inherit the provider's validated results for the requirements, or parts of requirements, they perform. You still document and evidence your own side of every shared requirement.

HITRUST says that in some cases up to 70% to 85% of requirements can be inherited from participating cloud providers. The real share depends on your scope and on how much of your environment runs on those services. Our guide to HITRUST inheritance from AWS, Azure and GCP covers it in detail.

What mistakes do first-timers make in MyCSF?

The most common first-timer mistakes are scoping too broadly, uploading evidence that doesn't match the requirement, leaving inheritance until the end, having no clear owner for each requirement and treating MyCSF as a document store rather than a working assessment. Each one adds back-and-forth with the assessor and slows the project down.

  • Scope creep. Every extra system adds requirements and evidence.
  • Generic evidence. One large policy uploaded against many requirements, with no pointer to the relevant section.
  • Late inheritance. Mapping inheritance after evidence is collected means redoing work.
  • No owners. Requirements without a named owner stall.
  • Last-minute uploads. Evidence collected in the final weeks often shows only a single point in time.

How should you get started with MyCSF?

Start by agreeing the assessment type and scope with your customer, then set up the assessment in MyCSF, assign an owner to each requirement, map inheritance early and run a readiness review before you invite your assessor. CyberWave GRC sets up and organizes MyCSF as part of HITRUST readiness, so your team can focus on the controls themselves.

A simple first-month plan:

  1. Confirm the assessment type and scope.
  2. Create the assessment in MyCSF and record your scoping answers.
  3. Map cloud inheritance.
  4. Assign requirement owners and agree an evidence format.
  5. Run a HITRUST readiness assessment to find the gaps.

For the full journey and the phases involved, read how long HITRUST certification takes. Our fee is fixed after a free scoping call; the HITRUST assessment and HITRUST Alliance fees are quoted separately.

Frequently asked questions

You need access to MyCSF to run a HITRUST assessment, because scoping, evidence and the validated assessment all happen there. HITRUST sets the access terms, so confirm what you need for your assessment type with HITRUST or your assessor. Any HITRUST Alliance fees are quoted separately from CyberWave GRC's fixed readiness fee.

Yes. Your team, your consultant and your Authorized External Assessor all work in the same assessment in MyCSF, each in their own role. CyberWave GRC helps with scoping, evidence and inheritance mapping, and Huduku AI, our independent assessor partner, tests controls and submits the validated assessment to HITRUST for review.

Yes. All three HITRUST assessments are run in MyCSF. The e1 covers 44 foundational controls and the i1 about 182 control requirements, while the r2 is tailored using risk factors from your scoping answers. The way you record answers, upload evidence and request inheritance is broadly the same across all three.
Hi! I'm your AI Assistant 💬