Vigyata.AI
Is this your channel?

Episode 19_PUBLICLY ACCESSIBLE CONTENT_ (AC-22)

1.4K views· 82 likes· 9:46· Jul 29, 2023

🛍️ Products Mentioned (4)

In this episode of the NIST SP 800-53 Rev 5 Security Control explanatory series, We reviewed the AC-22 PUBLICLY ACCESSIBLE CONTENT and then tried to simplify what the control requirements are all about, and how best to assess/test this control during the Security Control Assessment (SCA) process and self control assessment process in the Continuous Monitoring/On-Going Authorization phase of the RMF. Computer Security Resource Center https://csrc.nist.gov/publications The free way to help the channel grow is by subscribing using the link below: https://www.youtube.com/c/KamilSec?su... *************Patreon & Channel Support******************* https://www.patreon.com/kamilSec?fan_landing=true​ ********Order your KamilSec (KS) Designs Merch:********** https://kamilsec.creator-spring.com/ ************************************************************** CashApp: $Kamilzak Zelle: kaamilzak@gmail.com paypal: https://paypal.me/MZakari Venmo: @kamilsec Thank You!!! ************************************************************* **I ALSO CONDUCT INDIVIDUALIZED RESUME AND INTERVIEW PREP SESSION AS WELL AS ON THE JOB CONSULTATION** *************************************************************** ****Connect with me on Social Media***: Twitter: https://twitter.com/Kamilzak_1​ Instagram: @Kamilzak1 Facebook: https://www.facebook.com/kamil.kamilsec E-Mail: Kaamilzak@gmail.com

About This Video

In this Episode 19 of my NIST SP 800-53 Rev. 5 Access Control series, I wrap up the Access Control family by breaking down AC-22: Publicly Accessible Content. I walk through what the control is really trying to do: make sure the organization designates who is allowed to post publicly, trains those authorized individuals so they don’t accidentally publish non-public info, and puts a review/approval process in place before anything goes live—on the public website or on social media. I also highlight the ongoing requirement to review what’s already posted at an organization-defined frequency and remove non-public content if it’s discovered. I read the Rev. 5 requirement, hit the key points from the discussion, and simplify it into practical language: only vetted and approved information should be made public, and the process needs guardrails so mistakes get caught—especially through regular reviews. Then I go into how I assess/test AC-22 during an SCA or during continuous monitoring/ongoing authorization: I examine the SSP and access control policy/procedures, verify training requirements and actual training records, and request evidence like sample emails or ticketing artifacts (ServiceNow/Jira) showing review and approval prior to posting. I also call out a reality I see often—AC-22 is frequently marked N/A unless the agency truly deals with a lot of public-facing content.

Frequently Asked Questions

🎬 More from KamilSec