Password Security - Revision history

Lsilverman: /* Device Rules */

2020-10-16T17:06:31Z

Device Rules

Lsilverman: update Supported field (by SublimeText.Mediawiker)

2019-08-20T17:45:58Z

update Supported field (by SublimeText.Mediawiker)

Lsilverman: /* What to Do if You've been locked out of your Account */

2019-08-20T16:27:26Z

What to Do if You've been locked out of your Account

Jgullickson at 17:45, 29 December 2017

2017-12-29T17:45:57Z

Jvargo: /* Customizing It For You */

2017-05-11T19:04:14Z

Customizing It For You

Jvargo: /* Device Rules */

2017-05-11T18:59:04Z

Device Rules

Jvargo: /* Device Rules */

2017-05-11T18:57:45Z

Device Rules

Jvargo: /* Device Rules */

2017-05-11T18:55:55Z

Device Rules

Jvargo: /* Overview */

2017-05-11T18:49:22Z

Overview

Jvargo at 18:46, 11 May 2017

2017-05-11T18:46:48Z

@@ Line 28: / Line 28: @@
 **Must not contain 3 digit recurring patterns. EX: 123123
 **Must not sequentially increase or decrease for the whole Password. EX 1234567
-*'''Number of Historical Passwords to Keep''': The number of previous Passwords to retain for a user. When changing Passwords, users' Password cannot be one of their historical Passwords.
+*'''Prevent Password Re-use''': Allows for setting the number of previous Passwords to reject for user. User may not repeat any of their last X passwords, where X is configurable. TrackAbout does not store passwords in plain text, but rather stores a non-reversible, one-way cryptographic hash of the password. In this way, TrackAbout can check that a user's new password is not a repeat of an old password, while also not retaining any actual passwords in the database.
 **Setting this config to '0' will disable the historical Password check.

@@ Line 2: / Line 2: @@
 |Parent Module=Core Tracking
 |Feature Description=Protect data by ensuring password complexity and requirements are adequate
-|Supported In=TAMobile 5, TAMobile 6 Desktop, TAMobile 6 Rugged, TAMobile Android, TAMobile iOS
+|Supported In=TAMobile 6 Desktop, TAMobile 6 Rugged, TAMobile 7 Android, TAMobile 7 iOS
 }}
 ==Overview==

@@ Line 55: / Line 55: @@
 TrackAbout Support will not reset user passwords but will refer users to their local TrackAbout administrators for assistance.
-The local TrackAbout Administrator will be able to update user accounts through the [[Internal Users]] page
+The local TrackAbout Administrator will be able to update user accounts through the [[Internal Users]] page.
 ==Notes==

@@ Line 50: / Line 50: @@
 ==Customizing It For You==
 Your configuration preferences must be set by TrackAbout Support Staff.  Please reach out to TrackAbout Support to communicate your preferred settings.
 ==Notes==

@@ Line 49: / Line 49: @@
 ==Customizing It For You==
-Your configuration preferences must be set by TrackAbout Support Staff
+Your configuration preferences must be set by TrackAbout Support Staff.  Please reach out to TrackAbout Support to communicate your preferred settings.
 ==Notes==

@@ Line 29: / Line 29: @@
 **Must not sequentially increase or decrease for the whole Password. EX 1234567
 *'''Number of Historical Passwords to Keep''': The number of previous Passwords to retain for a user. When changing Passwords, users' Password cannot be one of their historical Passwords.
-*''''Setting to this config to '0' will disable the historical Password check.
+**Setting to this config to '0' will disable the historical Password check.
 ===Website Rules===

@@ Line 5: / Line 5: @@
 }}
 ==Overview==
-Password minimum requirements are configurable within TrackAbout.
+Password rules and minimum requirements are configurable within TrackAbout.
 ==Why You Need It==

@@ Line 1: / Line 1: @@
-==Summary ==
+{{TrackAbout Feature
 Password security is important.  It's important to keeping personal and business information safe and secure.  TrackAbout provides various options to establish secure password rules among your users.
 Here are the various Password configurations we have available:
+==How It Works==
-==Device Rules==
+===Device Rules===
 *'''Require Password on Login''': Determines whether or not a Password is required to log into the mobile unit.
@@ Line 19: / Line 27: @@
 **Must not contain 2 digit recurring patterns. EX: 1212xx
 **Must not contain 3 digit recurring patterns. EX: 123123
-**Must not increment or decrement for the whole Password. EX 1234567
+**Must not sequentially increase or decrease for the whole Password. EX 1234567
 *'''Number of Historical Passwords to Keep''': The number of previous Passwords to retain for a user. When changing Passwords, users' Password cannot be one of their historical Passwords.
 Setting to this config to '0' will disable the historical Password check.
-==Website Rules==
+===Website Rules===
 *'''Send Email When User Passwords Change''': When true, TrackAbout sends an email to users alerting them when their Passwords change.
@@ Line 29: / Line 37: @@
 *'''Password Allow Spaces And High Characters''': Allow spaces and high ASCII characters in WEBSITE Passwords.
 *'''Password Minimum Number Of Lower Case Letters''': Minimum number of lower case letters for WEBSITE Passwords.
-*'''Password Minimum Number Of Numbers''': Minimum number of lower case letters for WEBSITE Passwords.
+*'''Password Minimum Number Of Numeric Characters''': Minimum number of numeric characters for WEBSITE Passwords.
-*'''Password Minimum Number Of Special Characters''': Minimum number of special characters for WEBSITE Passwords.
+*'''Password Minimum Number Of Special Characters''': Minimum number of special characters for WEBSITE Passwords. EX: @#$%&*!
 *'''Password Minimum Number Of Upper Case Letters''': Minimum number of upper case letters for WEBSITE Passwords.
-==Rules Applying to Both Devices and Website ==
+===Rules Applying to Both Devices and Website ===
 *'''Password Expiry Warning Period in Days''': A Password expiration warning will be shown to the user starting from X days before the expiry date of the Password. Shows warnings in both the WEBSITE and Smartphone apps.
@@ Line 40: / Line 48: @@
 *'''Password Link Expiration Days''': Days after the Password recovery or new user link is sent until the link stops working. Use 0 for no expiration.
-==General ==
+==Customizing It For You==
 Regardless of where you're establishing a password, do not use colons in the creation.
 For web services, the username and password are sent as "username:password", which is a standard HTTP format for sending credentials. You will experience errors if we're parsing the username and password when the password contains a colon.