Must support the ability to disable user accounts and ensure no IV.M Operations Phase - disabled accounts can log in or Privacy and Security access the system. Must support the automatic disabling of user accounts if failed IV.M Operations Phase - logins exceed a configurable Privacy and Security threshold. Must automatically log off authenticated users after a configurable period of inactivity IV.M Operations Phase - and display a warning message to Privacy and Security the user prior to session timeout. Must support the saving of user profiles for archival purposes, IV.M Operations Phase - including the ability to Privacy and Security the profile. Must generate automatic alerts to system administrators when a IV.M Operations Phase - breach pattern or unauthorized use Privacy and Security activity is detected. Must provide appropriate encryption mechanisms to protect the confidentiality and integrity of critical data, including but not limited to passwords, social IV.M Operations Phase - security numbers and bank Privacy and Security account numbers. Must encrypt sensitive data in transit (including emails) to protect data confidentiality and integrity as IV.M Operations Phase - appropriate based on the Privacy and Security sensitivity of data. Must support the latest version of IV.M Operations Phase - Security Sockets Layer Privacy and Security (SSL)/Transport Layer Security. IV.M Operations Phase - Must prevent the creation of Privacy and Security duplicate accounts. Must support the use HTTPS/SSL IV.M Operations Phase - for connections between Privacy and Security interfaces.
IV.M Operations Phase - Privacy and Security Must support the ability to disable user accounts and ensure no disabled accounts can log in or access the system. IV.M Operations Phase - Privacy and Security Must support the automatic disabling of user accounts if failed logins exceed a configurable threshold. IV.M Operations Phase - Privacy and Security Must automatically log off authenticated users after a configurable period of inactivity and display a warning message to the user prior to session timeout. IV.M Operations Phase - Privacy and Security Must support the saving of user profiles for archival purposes, including the ability to the profile. IV.M Operations Phase - Privacy and Security Must generate automatic alerts to system administrators when a breach pattern or unauthorized use activity is detected. IV.M Operations Phase - Privacy and Security Must provide appropriate encryption mechanisms to protect the confidentiality and integrity of critical data, including but not limited to passwords, social security numbers and bank account numbers. IV.M Operations Phase - Privacy and Security Must encrypt sensitive data in transit (including emails) to protect data confidentiality and integrity as appropriate based on the sensitivity of data. IV.M Operations Phase - Privacy and Security Must support the latest version of Security Sockets Layer (SSL)/Transport Layer Security. IV.M Operations Phase - Privacy and Security Must prevent the creation of duplicate accounts. IV.M Operations Phase - Privacy and Security Must support the use HTTPS/SSL for connections between interfaces.
4%20Attachment%20B%20-%20Business%20and%20Technical%20Requirements%20Matrix.docx