Comments (3)
I went to listen to the talk which is here: https://youtu.be/O0gDd8jXgfY?t=25014
So, my understanding is that mudge is saying that SMS does offer good protection (albeit depending on the scenario). He is not saying we shouldn't advocate for other mechanisms as well. Just because it is good enough for a user, doesn't mean the application should not also offer something stronger.
2.2.2 currently says:
....Verify that restricted authenticators (those using PSTN to deliver OTPs via phone or SMS) are offered only when alternate stronger methods are also offered and when the service provides information on their security risks to users.
We are not saying don't use it, we are saying allow stronger methods as well and be clear about the risks. As such, I am comfortable with the current wording.
from asvs.
NIST released the Special Publication 800-63B as a guideline for digital identity guidelines which includes three levels of authentication strength. The Authenticator Assurance Levels (AALs) define the strength of the authentication process. There are three levels:
AAL1: Provides some assurance that the claimant controls the authenticator.
AAL2: Provides high confidence that the claimant controls the authenticator.
AAL3: Provides very high confidence that the claimant controls the authenticator.
Relation between SMS MFA and AALs:
AAL1: At this level, SMS-based MFA can be considered acceptable. AAL1 allows for a wide range of authenticators, including weaker ones. However, it's worth noting that even at this level, the use of SMS-based MFA has been criticized due to vulnerabilities like SIM swapping, interception, and social engineering attacks.
AAL2: This level requires at least two distinct authentication factors. While SMS-based MFA could technically be used as one of the factors, NIST 800-63B has expressed reservations about its use. Specifically, the guidelines recommend against the use of out-of-band authentication using the PSTN (public switched telephone network), which includes SMS. The concerns arise from the potential for interception and redirection of SMS messages.
AAL3: At this highest assurance level, the requirements are even stricter. The use of SMS-based MFA would not be recommended or considered secure enough for AAL3 due to the aforementioned vulnerabilities and the potential for sophisticated attacks.
from asvs.
I think our aim is potentially to follow the AAL model so if anyone thinks our current wording does not do so then please open a separate issue so we can reevaluate :)
from asvs.
Related Issues (20)
- Request for Reevaluation of ASVS Item 10.3.3 Related to Subdomain Takeovers HOT 26
- Masking Sensitive Information in Category 8 HOT 23
- Discourage the use of Stateless Sessions (and therefor the usage of JWT for session) HOT 10
- Consideration for Memcache Injection Vulnerabilities HOT 16
- Consideration for Excluding Item 14.5.6 HOT 4
- 7.2 covering "Security Events" HOT 1
- 1.7.1 - do we need to require common logging format? HOT 6
- Section and requirement relevance questions HOT 2
- Consideration for HTTP/3 Security HOT 6
- Suggestion for Reconsideration of ASVS Requirement 8.3.1 Classification HOT 6
- Opportunistic Session Termination HOT 20
- recommendations chapter HOT 3
- Require case-sensitive password matching? HOT 11
- 14.4 section (HTTP Security Headers) rename / find better category-section for "content-type" requirements. HOT 2
- proposal: new requirement for disallowing search engines to crawl and index the content HOT 8
- 2.2.2 and 2.7.1 are duplicates HOT 2
- 2.7.5 is a security problem and weakness HOT 8
- 2.7.6 and 2.7.7 are in conflict HOT 6
- discussion/proposal: disallow user-autologin to an application using SSO sessions HOT 3
- Inclusion of Cypher Injection Prevention for Neo4j in ASVS 5.3.4 HOT 2
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from asvs.