For customers not using SSO, do you have documented password/passphrase reset procedures that are currently implemented in the system and/or customer support?
Explanation
Example Responses
Example Response 1
Yes, we maintain comprehensive password reset procedures for non-SSO users Our system implements a self-service password reset functionality that requires users to verify their identity through a combination of security questions and a one-time verification code sent to their registered email address Temporary passwords expire after 24 hours and require immediate change upon first login For situations requiring customer support intervention, our documented procedures require support staff to verify at least two pieces of identifying information (such as account details and contact information) before initiating a password reset All password reset activities are logged for audit purposes, and our procedures are reviewed annually as part of our security program.
Example Response 2
Yes, our organization has documented password reset procedures for non-SSO users that are currently implemented both through our system and customer support channels For self-service resets, users must verify their identity using a multi-factor approach: they must provide their username, answer a pre-registered security question, and then receive a verification code via SMS to their registered phone number Our customer support team follows a documented verification protocol requiring confirmation of the user's full name, date of birth, and the last four digits of their registered phone number before processing manual resets All reset requests generate a temporary password valid for 4 hours and trigger an email notification to the user's registered email address These procedures are documented in our Information Security Policy and reviewed quarterly.
Example Response 3
No, we currently do not have formally documented password reset procedures for non-SSO users While our customer support team does handle password reset requests on a case-by-case basis, we lack standardized verification protocols and documentation for this process We recognize this as a security gap in our current operations and are in the process of developing formal procedures that will include proper identity verification steps, secure temporary password delivery methods, and comprehensive documentation We expect to have these procedures finalized and implemented within the next 60 days, after which they will be incorporated into our regular security review cycle.
Context
- Tab
- Product
- Category
- Authentication, Authorization, and Account Management

