You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
the list of Permitted Authenticator Types for AAL3 (4.3.1.) does not match the AAL Summary of Requirements for AAL3 (Table 4-1).
List from 4.3.1 (just the relevant entries):
· Multi-Factor OTP device (software or hardware) (Section 5.1.5) used in conjunction with a Single-Factor Cryptographic Device (Section 5.1.7)
· Multi-Factor OTP Device (hardware only) (Section 5.1.5) used in conjunction with a Single-Factor Cryptographic Software (Section 5.1.6)
· Single-Factor OTP Device (hardware only) (Section 5.1.4) used in conjunction with a Multi-Factor Cryptographic Software Authenticator (Section 5.1.8)
While the correspondent relevant entries of Table 4-1 say this
· SF OTP Device plus MF Crypto Device or Software;
Section 4.3.1 is correct. In the meanwhile, note that Table 4-1 is informative (in anticipation that an inconsistency of this sort might arise).
The text was updated successfully, but these errors were encountered:
the list of Permitted Authenticator Types for AAL3 (4.3.1.) does not match the AAL Summary of Requirements for AAL3 (Table 4-1).
List from 4.3.1 (just the relevant entries):
· Multi-Factor OTP device (software or hardware) (Section 5.1.5) used in conjunction with a Single-Factor Cryptographic Device (Section 5.1.7)
· Multi-Factor OTP Device (hardware only) (Section 5.1.5) used in conjunction with a Single-Factor Cryptographic Software (Section 5.1.6)
· Single-Factor OTP Device (hardware only) (Section 5.1.4) used in conjunction with a Multi-Factor Cryptographic Software Authenticator (Section 5.1.8)
While the correspondent relevant entries of Table 4-1 say this
· SF OTP Device plus MF Crypto Device or Software;
Section 4.3.1 is correct. In the meanwhile, note that Table 4-1 is informative (in anticipation that an inconsistency of this sort might arise).
The text was updated successfully, but these errors were encountered: