12 ms·
This does not address the core complaint from the breach[1]: > 18F’s use of both OAuth 2.0 and Slack is not in compliance with GSA’s Information Technology Sta
by tyre 10y ago
This does not address the core complaint from the breach[1]:
> 18F’s use of both OAuth 2.0 and Slack is not in compliance with GSA’s Information Technology Standards Profile, GSA Order
CIO P 2160.1E. The order allows information technologies to be
approved for use in the GSA IT environment if they comply with
GSA’s security, legal, and accessibility requirements. Currently, neither OAuth 2.0 nor Slack are approved for use in the GSA IT standards profile.
> ...
> The OIG makes the following recommendations:
> 1. GSA should cease using Slack and OAuth 2.0 until and
unless they are approved for use in the IT Standards Profile.
> 2. GSA should ensure that 18F complies with GSA Order CIO
P 2160.1E.
Is 18F no longer using Slack or any other OAuth 2.0 integrations? That would be a shame. Are they working with GSA and the Office of Inspections and Forensic Auditing to clear Slack/OAuth 2.0?
[1]: https://www.gsaig.gov/sites/default/files/ipa-reports/Alert%20Report-GSA%20Data%20Breach%205.12.16.pdf https://www.gsaig.gov/sites/default/files/ipa-reports/Alert%...
- rajivm 10y agoI would imagine this is not so much that OAuth 2.0 is a problem so much as granting the "Drive" scope via OAuth 2.0 grants access to ALL Google Drive files the user has access to.
- untog 10y agoWell, no, OAuth 2.0 is the problem, but only because it hasn't been government certified.
- deleted 10y ago[deleted]
- dsl 10y agoFrom what I have seen the government has approved and prefers SAML over OAuth intentionally.