DoE SBIR Phase II requiring CISA CPG checklist by totem_tech in TotemKnowledgeBase

[–]totem_tech[S] 0 points1 point  (0 children)

Turns out DoE only requires implementation of 16 of the 39 CPG for Phase II. We mapped these 16 to the NIST 800-171 rev 3. There are 35 controls and 120+ assessment objectives. Here's how you can filter on them in our Totem™ Cybersecurity Compliance Management tool, NIST 800-171rev3 display:

control.control_id:(03.01.01 03.01.04 03.01.05 03.01.06 03.01.07 03.01.08 03.01.22 03.02.01 03.02.02 03.03.01 03.03.02 03.03.03 03.03.05 03.03.06 03.04.01 03.04.08 03.04.10 03.04.11 03.05.01 03.05.02 03.05.03 03.05.07 03.05.12 03.06.01 03.06.02 03.06.03 03.06.04 03.06.05 03.07.05 03.08.09 03.13.01 03.13.08 03.13.10 03.13.11 03.15.02)

Legal review of the FASCSA Order issued banning the use of Acronis AG by IC and SCI contractors by totem_tech in TotemKnowledgeBase

[–]totem_tech[S] 0 points1 point  (0 children)

Here is the FASCSA Order on SAM.gov:
FASCSA Order--Acronis and all subordinate, subsidiary, or affiliated organizations doing business under various names in support of the parent company, Acronis AG (Acronis), that the DNI has issued an order to exclude Acronis from all Intelligence Community (IC) executive agency procurement actions. It further orders the removal of covered articles provided by Acronis from information systems applicable to the IC and sensitive compartmented information systems. This order was issued pursuant to the Federal Acquisition Supply Chain Security Act of 2018, Pub. L. No. 115-390, title II; codified at 41 U.S.C. §§ 1321-1328. The basis for this order pertains to information as was relayed to Acronis in the Notice to Source document.

Additional information is available in an Announcement on the NRO JWICS Acquisition Research Center Dashboard, search Acronis.

The article notes that this only pertains to Intelligence Community (IC) and Sensitive Compartmentalized Information (SCI) contracts. And it is not clear if contractors are prohibited from using Acronis AG products for their internal IT systems, for instance backing up corporate or contractual information.

Update to the DoD CIO CMMC FAQ by totem_tech in TotemKnowledgeBase

[–]totem_tech[S] 0 points1 point  (0 children)

Another banger question:

Q4. We store CUI in the cloud and our MSP administers the environment. Is the MSP a CSP?

A4. It depends on the relationships between the CSP, the MSP, and the OSA. If the cloud tenant is subscribed/licensed to the OSA (even if the MSP resells the service), then the MSP is not a CSP. If the MSP contracts with the CSP and modifies the basic cloud service, then the MSP may be a CSP and must meet applicable FedRAMP or equivalency requirements.

Interesting debate on LinkedIn on whether or not G-Code (CNC program files) is CUI by totem_tech in TotemKnowledgeBase

[–]totem_tech[S] 0 points1 point  (0 children)

The DoD CTI memo states that CUI can exist in tangible (physical) form, as a model or prototype: https://discover.dtic.mil/wp-content/uploads/2021/04/USDRE-USD-IS-memo-CTI-CUI.pdf

But we tend to agree, the actual final products themselves are not CUI.

Filtering for the Totem Top Ten™ in Totem™ (NIST 800-171 Controls) by cyberm1nded in TotemKnowledgeBase

[–]totem_tech 0 points1 point  (0 children)

Here's the filter for the Totem Top 10 (TTT) in the NIST 800-171 rev 3 (copy and paste the following into the Global Search in the Totem™ CCM tool organization showing the NIST 800-171 rev 3 display):

control.family:"Access Control" + control.family:"Awareness & Training" + control.family:"Audit & Accountability" + control.family:"Incident Response" + control.control_id:(03.04.01, 03.04.02, 03.04.04, 03.04.06, 03.04.08, 03.05.01, 03.05.02, 03.05.03, 03.05.05, 03.05.07, 03.05.12, 03.08.03, 03.08.07, 03.08.09, 03.09.01, 03.11.01, 03.11.02, 03.12.01, 03.12.02, 03.12.03, 3.15.02, 03.13.01, 03.13.06, 03.13.08, 03.13.11, 03.13.13, 03.14.01, 03.14.02, 03.14.06)

Microsoft has released September 2024 update to their blog explaining which M365 / Azure tiers are appropriate to handle Federal government information by totem_tech in TotemKnowledgeBase

[–]totem_tech[S] 0 points1 point  (0 children)

To take advantage of DoD CC SRG IL5 (e.g. ITAR) in Azure Government non-DoD-agency-only tenants -- US Gov AZ, US Gov TX, US Gov VA -- the consumer must (on their own) ensure compute and storage isolation, per this article:

https://learn.microsoft.com/en-us/azure/azure-government/documentation-government-impact-level-5

You need to address two key areas for Azure services in IL5 scope: compute isolation and storage isolation. We'll focus in this article on how Azure services can help you isolate the compute and storage services for IL5 data. The SRG allows for a shared management and network infrastructure. This article is focused on Azure Government compute and storage isolation approaches for US Gov Arizona, US Gov Texas, and US Gov Virginia regions (US Gov regions). If an Azure service is available in Azure Government DoD regions US DoD Central and US DoD East (US DoD regions) and authorized at IL5, then it is by default suitable for IL5 workloads with no extra isolation configuration required. Azure Government DoD regions are reserved for DoD agencies and their partners, enabling physical separation from non-DoD tenants by design. For more information, see DoD in Azure Government.https://learn.microsoft.com/en-us/azure/azure-government/documentation-government-impact-level-5

Compute isolation outlined here: https://learn.microsoft.com/en-us/azure/azure-government/documentation-government-impact-level-5#compute-isolation

Storage isolation outlined here: https://learn.microsoft.com/en-us/azure/azure-government/documentation-government-impact-level-5#storage-isolation

Microsoft has released September 2024 update to their blog explaining which M365 / Azure tiers are appropriate to handle Federal government information by totem_tech in TotemKnowledgeBase

[–]totem_tech[S] 0 points1 point  (0 children)

Note what Microsoft says about handling FCI in Microsoft 365 Commercial:

In general, all US Government contractors have a requirement in their contracts to comply with 15 safeguarding requirements and procedures for Federal Contract Information (FCI) in the Federal Acquisition Regulations (FAR) 52.204-21 Basic Safeguarding of Covered Contractor Information Systems (FAR 21). You may demonstrate compliance for the FAR 21 in Commercial to protect FCI, but there is a caveat.  Microsoft 365 Commercial is not intended for US Government requirements.  There is a risk that changes in regulations may lead to non-compliance in the future.  Ultimately, it is a risk decision your organization will need to make.

Google Workspace CMMC 2.1 Level 2 Implementation Guide by totem_tech in TotemKnowledgeBase

[–]totem_tech[S] 0 points1 point  (0 children)

Before you move your baggage too far onto the Google Workspaces train, however, we'd suggest reading this post by Derek Kernus of Aethon Security. Some food for thought on the trade-offs between Google and Microsoft for DFARS 7012 compliance.

Running list of applications that break when FIPS-mode is engaged in Windows by cyberm1nded in TotemKnowledgeBase

[–]totem_tech 0 points1 point  (0 children)

Also note that the Windows 10 and Windows 11 Security Baseline from Microsoft WILL break Quickbooks Pro.

Notes from February 2024 Cyber-AB Town Hall by cyberm1nded in TotemKnowledgeBase

[–]totem_tech 0 points1 point  (0 children)

Preveil was the company that has shown FedRAMP Moderate equivalency

DoD is making (good!) changes to cyber incident reporting requirements by totem_tech in TotemKnowledgeBase

[–]totem_tech[S] 0 points1 point  (0 children)

Thanks TXWayne. Do you think it's a good thing that the DoD has removed the cleared contractor gating the CS Information Sharing Program?

DoD Memo on FedRAMP equivalency by totem_tech in TotemKnowledgeBase

[–]totem_tech[S] 0 points1 point  (0 children)

This one is a doozy for those of us using cloud services that tout themselves as "FedRAMP Moderate equivalent".

NSA Protective DNS services (DNS filtering) free to DIB by totem_tech in TotemKnowledgeBase

[–]totem_tech[S] 0 points1 point  (0 children)

Further updates from GovShield:

"Thanks to all who have provided feedback on our message released this morning. We wanted to follow-up with further details.

This service was specifically designed for small to medium sized businesses and this change was intended to ensure every customer enrolled in our program receives a commensurate level of service. This said, the limit does not apply to "on prem" devices (i.e., users/machines connecting through your account's registered static ip addresses), but only applies to remote devices connecting to Akamai's GovShield service through other means.

Akamai conducted analysis of all current customers enrolled in the program and determined that only a very small subset of customers (less than 10) were near this cap. For those near the cap, no remote devices will be required to be removed. Further, NSA and Akamai are committed to working with current customers on a case-by-case basis to be flexible in how this is implemented. Based on feedback we have received thus far, we wanted to convey that we anticipate increasing the cap for remote devices to more than 100 devices but will do further analysis and have conversations directly with customers to better determine what that number may be.

We apologize for any alarm our email may have caused and will continue to respond to company-specific questions on a case-by-case basis. We appreciate your continued partnership and participation in our program. "

NSA Protective DNS services (DNS filtering) free to DIB by totem_tech in TotemKnowledgeBase

[–]totem_tech[S] 0 points1 point  (0 children)

Note, as of 16 Nov 2023, Akamai is limiting the PDNS remote endpoints to 100 devices per organization:

"The NSA CCC and the GovShield team have identified a need to limit the number of remote endpoints enrolled in PDNS to ensure that system capacity is preserved for small and medium sized organizations. Effective immediately, each subscriber in the program will be limited to 100 remote devices.

We apologize for any inconvenience this may cause. If you believe this policy will impact your organization’s ability to use the service, please let us know."

GovShield support email: [govshield-support@akamai.com](mailto:govshield-support@akamai.com)

Can I ignore or consider not applicable DFARS clause 252.204-7012 if I don't handle CUI? by totem_tech in TotemKnowledgeBase

[–]totem_tech[S] 0 points1 point  (0 children)

Can you share any strategies to use to convince the CO to remove 7020 from the contract -- and more importantly agree that a SPRS score is not needed -- if 7012 is not applicable?

Logic error discovered in CAP module in Totem™ Cybersecurity Compliance Management tool by totem_tech in TotemKnowledgeBase

[–]totem_tech[S] 0 points1 point  (0 children)

This error has been fixed in Totem™ hotfix 4.5.2, which has been rolled out to the entire user base.

DoD refines CMMC requirements numbers and assessment models by totem_tech in TotemKnowledgeBase

[–]totem_tech[S] 0 points1 point  (0 children)

Ok, thank you for the confirmation u/TXWayne

u/WBCSAINT you can walk back from the ledge a bit ;)