Example, read only. A sample company whose own team runs its CMMC program here, reviewed by a credentialed officer and kept current.

← All 17 practicesPractice 4 of 17 · AC.L1-3.1.22
AC · Access ControlMET

AC.L1-3.1.22 · FAR 52.204-21 (b)(1)(iv) · NIST SP 800-171 3.1.22

Control Public Information

Control information posted or processed on publicly accessible information systems

Reviewed by a credentialed officer on June 12, 2026. The officer advises and never signs; this corroborates your own self assessment and certifies nothing. The finding, and the affirmation, stay yours.

Who is accountable for this safeguard

They get the reminder when this evidence goes stale. Carries into next year's cycle.

RCRaymond T. Cedar, Owner and President

What it means

Make sure nobody posts federal contract info on your public website, a public blog, or social media.

Why it matters

FCI posted publicly is a direct contract breach and an automatic rejection. One careless social-media post by a junior employee is the usual failure mode, policy plus review is the control.

The proof on file

  • Access Control Policy (Policy Center)From your Policy Center · May 20, 2026On file
  • website-content-review-q2.pdfUploaded, checked by Charlie · June 3, 2026Sufficient

Every uploaded file is checked by Charlie the moment it arrives, so a gap is caught on the spot, not at the assessment. Pulls from Microsoft 365 and references to the Policy Center and registers come straight from where they live, so they skip that check.

The narrative on file

Cedar Ridge has no public website posting area and no social accounts that publish federal work. The owner reviews the company site quarterly to confirm no drawings, quotes, or contract details are ever posted publicly.

You answer in plain English. Charlie drafts the narrative for your System Security Plan, and you confirm it.

What makes it pass

  • A written policy stating FCI may not be posted to public surfaces without owner review
  • Acknowledgement signatures from every employee
  • A recent quarterly review entry (date + surfaces reviewed + findings)
  • For M365 path: SharePoint sharing settings showing FCI sites are not public

Assessment objectives, NIST SP 800-171A

[a] Individuals authorized to post or process information on publicly accessible systems are identified
MET
[b] Procedures to ensure FCI is not posted or processed on publicly accessible systems are identified
MET
[c] A review process exists prior to posting public content
MET
[d] Public content is reviewed to ensure it does not include FCI
MET
[e] Mechanisms exist to remove and address improper posting of FCI
MET
Safeguard complete · MET

The team at Cedar Ridge Machine Works, LLC confirmed this safeguard MET. The evidence above is a living document: refresh rosters, devices, and accounts whenever the business changes and the safeguard stays current. The single signature happens in Attest & file, once all 17 are met.

Next safeguard →
Need the exact clicks?Microsoft 365 (SharePoint / OneDrive), step by step
  1. 1Go to admin.microsoft.com → SharePoint admin center → Policies → Sharing
  2. 2Confirm external sharing is restricted (or off for sites containing FCI)
  3. 3Screenshot the sharing policy

Capture: Screenshot of external sharing settings showing FCI sites are not publicly accessible.

This is one of 17

Answer in plain English, file the proof, confirm it MET.

The team at Cedar Ridge Machine Works, LLC walked all 17 the same way. The platform explains each one in plain English and tells you what proof to grab or pulls it from Microsoft 365, Charlie drafts the paperwork with you, a credentialed officer reviews it, and your team confirms each one MET. The self assessment stays your act. Start free for 30 days, no credit card, or book a free advisory call if you would rather talk it through first.