Remix clone Hacker News

I ask, because according to MS...

"GPT-4o is now available as part of Azure OpenAI Service for Azure Government and included as part of this latest FedRAMP High and DoD IL4/IL5 Authorization."

...we have everything setup in Azure but are weary to start using with CUI. Our DoD contacts think it's good to go, but nobody wants to go on record as giving the go-ahead.

https://devblogs.microsoft.com/azuregov/azure-openai-fedramp...

https://learn.microsoft.com/en-us/azure/azure-government/com...

▲

cuuupid 3 hours ago | parent | next [-]

Ah by “it” I meant OpenAI commercial. Azure OpenAI can handle CUI Basic.

They also have a deployment on SIPR rated for secret.

Anything higher, you need a special key but AWS Bedrock has Claude up on C2S.

That being said both Azure OpenAI and AWS Bedrock suck for many reasons and they will by default extend your system boundary (meaning you need to extend your ATO). Also, for CUI, it has the P-ATO from JAB, not many agency specific ATOs, which means you will probably need to submit it thru your agency sponsor.

▲

starfezzy 5 hours ago | parent | prev [-]

Have they given a reason for being hesitant? The whole point of IL4+ is that they handle CUI (and higher). The whole point of services provided for these levels is that they meet the requirements.

	▲	subroutine 4 hours ago \| parent [-]
		The following is required from the company using a provisionally authorized vendor service: * organization required to perform a Risk Assessment (is this standardized?) * organization must issue an Authority to Operate (ATO) (example? to whom?) to use it for CUI as the data owner. * organization must ensure data is encrypted properly both at rest and in transit (is plain text typed into a chat window encrypted at rest?). * organization must ensure the system is documented in a System Security Plan (SSP) (example?). * organization must get approval from government sponsor of each project to use CUI with AI tools I am the one pushing for adoption, but don't have the time or FedRAMP/DISA expertise, and our FSO/CISO would rather we just not.