MASWE-0033: Authentication or Authorization Protocol Security Best Practices Not Followed

Content in BETA

This content is in beta and still under active development, so it is subject to change any time (e.g. structure, IDs, content, URLs, etc.).

Send Feedback

Draft Weakness

This weakness hasn't been created yet and it's in draft. But you can check its status or start working on it yourself. If the issue has not yet been assigned, you can request to be assigned to it and submit a PR with the new content for that weakness by following our guidelines.

Check our GitHub Issues for MASWE-0033

Initial Description or Hints

For example, when using oauth2, the app does not use PKCE, etc. See RFC-8252. Focus on client-side best practices.

Relevant Topics

• best practices from RFC-8252
• SSO -> OpenID Connect (OIDC)
• use of Google Service Accounts
• use of RISC
• use of Apple Redirect extensions for Enterprise
• using use SFAuthenticationSession (deprecated) instead of ASWebAuthenticationSession
• secure mutual authentication using X.509v3 certificates
• use of context to add security to authentication e.g. via IP or location data
• set prefersEphemeralWebBrowserSession to true before calling start for a session on iOS

References

• https://mobidev.biz/blog/single-sign-on-sso-implementation-benefits-enterprise
• https://developers.google.com/identity/protocols/risc
• https://developer.apple.com/documentation/authenticationservices/aswebauthenticationsession/3237231-prefersephemeralwebbrowsersessio?language=objc
• https://developer.apple.com/videos/play/tech-talks/301
• https://developers.google.com/identity/protocols/oauth2

MASTG v1 Coverage

No MASTG v1 tests are related to this weakness.