We are in the process of creating a procedure in the case of a security breach in which we might need to have all members change their online banking passwords. If we had to force a password change, can the system recognize old passwords and not allow them to be used again?

Search

Tools

For a forced password change, the security table can be flooded with a forced password change status and the member would have to change their password the next time they log in. The hold password would remain in the system until the member updates their password.

There is not an automated process for this on CU*BASE. A programmer will have to do this manually via a custom programming request. A custom request would need to be submitted and an estimate for leadtime will be provided at that time. As a rule of thumb for custom projects, a programmer will generally be assigned within 60 to 90 days after the bid has been signed and returned to CU*Answers. This estimate is based on not knowing what the number or scope of projects in the custom programming queue will be when a bid is signed & returned. The Developer's Help Desk (DHD) team does offer to escalate projects (which puts the project at the top to be assigned next to a programmer). This will incur an additional fee, on top of the bid amount for the programming itself. Reach out to the Client Services & Education team to get the process started.

As far as reusing passwords, we do not currently have a system in place to prevent users from reusing an old password, as we do not keep historical records of passwords against which to make that verification.