Security setup - Revision history

Kpe: /* Multi-factor Authentication (recommended) */

2025-06-06T07:55:19Z

Multi-factor Authentication (recommended)

@@ Line 49: / Line 49: @@
 === Multi-factor Authentication (recommended) ===
 TS No-code Platform offers native Multi-factor Authentication to protect against unauthrised access by requiring a user to provide multiple authentication factors to prove their identity. At present two different options are available:
 * MFA using session-specific, one-time-passcodes sent to the users mobile phone via regular or Flash SMS
@@ Line 61: / Line 63: @@
 '''Note:''' If using singlesignon (SSO) the MFA will not be used
 === Geolocation blocking (optional) ===

Kpe: /* Compliance external */

2024-11-09T12:40:46Z

Compliance external

← Older revision		Revision as of 14:40, 9 November 2024
Line 176:		Line 176:

	Depending on your security setup you might want to log these to a central repository		Depending on your security setup you might want to log these to a central repository


			== Other optional security features ==
			* [[Security/Data restrictions\|Data restrictions]]
			* [[Security/Encryption\|SSL encryption]]
			* [[Security/Bruteforce\|Bruteforce countermeasures]]

Kpe: /* Password Policies (recommended) */

2024-11-09T12:36:03Z

Password Policies (recommended)

← Older revision		Revision as of 14:36, 9 November 2024
Line 37:		Line 37:
	* Maximum password age		* Maximum password age
	* Maximum number of tries		* Maximum number of tries

			The struictural restrictions will be honored when
			* The user changes his password
			* A new randow password is generated and sent

			Passwords can also be set to expire after an amount of time.

	'''How to:''' The polices can be changed in server configurations in the group ''Password policies''		'''How to:''' The polices can be changed in server configurations in the group ''Password policies''

Nun: /* Security by design */

2023-08-10T13:56:42Z

Security by design

← Older revision		Revision as of 15:56, 10 August 2023
Line 5:		Line 5:
	The platform is security designed in accordance with [https://owasp.org/www-pdf-archive/OWASP_Application_Security_Verification_Standard_4.0-en.pdf OWASP version 4]:		The platform is security designed in accordance with [https://owasp.org/www-pdf-archive/OWASP_Application_Security_Verification_Standard_4.0-en.pdf OWASP version 4]:
	* Level 2: Compliant		* Level 2: Compliant
	* Level 3: +90% ~~supportede~~		* Level 3: +90% supported

	In addition the platform supports a wide range of security schemes and logging features, needed for support of ISO27001, ISAE3000 etc.		In addition the platform supports a wide range of security schemes and logging features, needed for support of ISO27001, ISAE3000 etc.

Nun at 13:56, 10 August 2023

2023-08-10T13:56:32Z

← Older revision		Revision as of 15:56, 10 August 2023
Line 5:		Line 5:
	The platform is security designed in accordance with [https://owasp.org/www-pdf-archive/OWASP_Application_Security_Verification_Standard_4.0-en.pdf OWASP version 4]:		The platform is security designed in accordance with [https://owasp.org/www-pdf-archive/OWASP_Application_Security_Verification_Standard_4.0-en.pdf OWASP version 4]:
	* Level 2: Compliant		* Level 2: Compliant
	* Level 3: +90% ~~supported~~		* Level 3: +90% supportede

	In addition the platform supports a wide range of security schemes and logging features, needed for support of ISO27001, ISAE3000 etc.		In addition the platform supports a wide range of security schemes and logging features, needed for support of ISO27001, ISAE3000 etc.

Tvi: 79 revisions imported

2021-12-10T10:55:28Z

79 revisions imported

← Older revision	Revision as of 12:55, 10 December 2021
(No difference)

80.161.14.74: /* Activity and data logging (optional) */

2021-11-16T15:27:23Z

Activity and data logging (optional)

← Older revision		Revision as of 17:27, 16 November 2021
Line 119:		Line 119:
	Activity and Data Logging includes the automatic creation of a series of log files. Logging can be set up for each entity in an application providing insight and transparency in relation to: user activity, creation, changes and status of different records in an application.		Activity and Data Logging includes the automatic creation of a series of log files. Logging can be set up for each entity in an application providing insight and transparency in relation to: user activity, creation, changes and status of different records in an application.
	* '''Access Log''': Can be activated on an entity in an application. This automatically generates a log of which users have accessed and/or edited a given record.		* '''Access Log''': Can be activated on an entity in an application. This automatically generates a log of which users have accessed and/or edited a given record.
	* '''Status ~~log~~''': Can be activated for an entity in an application. This automatically generates a log of the history of the created records, which shows how long a record has been in each status		* '''Status Log''': Can be activated for an entity in an application. This automatically generates a log of the history of the created records, which shows how long a record has been in each status
	* '''Change ~~log~~''': Can be activated for an entity in an application. This automatically generates a log of what changes have been made to the individual records. Including who has changed what and when (timestamp).		* '''Change Log''': Can be activated for an entity in an application. This automatically generates a log of what changes have been made to the individual records. Including who has changed what and when (timestamp).

	'''How to:''' Each option is activated on the entity Advanced page.		'''How to:''' Each option is activated on the entity Advanced page.

80.161.14.74: /* Versioning (optional) */

2021-11-16T15:22:17Z

Versioning (optional)

← Older revision		Revision as of 17:22, 16 November 2021
Line 127:		Line 127:

	=== Versioning (optional) ===		=== Versioning (optional) ===
	By default file versioning is supported on ~~document fields~~.		By default file versioning is supported on the "Documents" and "Files" field types. In addition, data revisions can be supported on each entity. This automatically builds an audit log for each record.

	In addition data revisions can be supported on each individual entity.		In addition data revisions can be supported on each individual entity.

80.161.14.74: /* Activity and data logging (optional) */

2021-11-16T15:18:30Z

Activity and data logging (optional)

← Older revision		Revision as of 17:18, 16 November 2021
Line 118:		Line 118:
	=== Activity and data logging (optional) ===		=== Activity and data logging (optional) ===
	Activity and Data Logging includes the automatic creation of a series of log files. Logging can be set up for each entity in an application providing insight and transparency in relation to: user activity, creation, changes and status of different records in an application.		Activity and Data Logging includes the automatic creation of a series of log files. Logging can be set up for each entity in an application providing insight and transparency in relation to: user activity, creation, changes and status of different records in an application.
	* '''Access Log''': ~~can~~ be activated on an entity in an application. This automatically generates a log of which users have accessed and / or edited a given record.		* '''Access Log''': Can be activated on an entity in an application. This automatically generates a log of which users have accessed and/or edited a given record.
	* Status log: ~~History~~ of ~~items time spent~~ in each ~~step~~		* '''Status log''': Can be activated for an entity in an application. This automatically generates a log of the history of the created records, which shows how long a record has been in each status
	* Change log: ~~Copy~~ of ~~old data along with timestamp and user that~~ has changed ~~the item~~ (~~see below~~)		* '''Change log''': Can be activated for an entity in an application. This automatically generates a log of what changes have been made to the individual records. Including who has changed what and when (timestamp).

	'''How to:''' Each option is activated on the entity Advanced page.		'''How to:''' Each option is activated on the entity Advanced page.

80.161.14.74: /* Activity and data logging (optional) */

2021-11-16T15:14:48Z

Activity and data logging (optional)

← Older revision		Revision as of 17:14, 16 November 2021
Line 118:		Line 118:
	=== Activity and data logging (optional) ===		=== Activity and data logging (optional) ===
	Activity and Data Logging includes the automatic creation of a series of log files. Logging can be set up for each entity in an application providing insight and transparency in relation to: user activity, creation, changes and status of different records in an application.		Activity and Data Logging includes the automatic creation of a series of log files. Logging can be set up for each entity in an application providing insight and transparency in relation to: user activity, creation, changes and status of different records in an application.
	* '''Access ~~:og~~''': can be activated on an entity in an application. This automatically generates a log of which users have accessed and / or edited a given record.		* '''Access Log''': can be activated on an entity in an application. This automatically generates a log of which users have accessed and / or edited a given record.
	* Status log: History of items time spent in each step		* Status log: History of items time spent in each step
	* Change log: Copy of old data along with timestamp and user that has changed the item (see below)		* Change log: Copy of old data along with timestamp and user that has changed the item (see below)