Audits - Revision history

Jeffrey at 18:34, 22 June 2015

2015-06-22T18:34:48Z

Jeffrey at 18:29, 22 June 2015

2015-06-22T18:29:30Z

Stage at 04:12, 18 May 2015

2015-05-18T04:12:47Z

Stage at 15:35, 17 May 2015

2015-05-17T15:35:22Z

Stage at 05:19, 10 May 2015

2015-05-10T05:19:20Z

Stage at 05:18, 10 May 2015

2015-05-10T05:18:59Z

Stage at 17:43, 9 May 2015

2015-05-09T17:43:11Z

Stage: Created page with "All changes made to the data in the software are audited and the audit log is maintained in the database. Two types of auditing records are maintained: 1. Every record in e..."

2015-05-08T19:13:27Z

Created page with "All changes made to the data in the software are audited and the audit log is maintained in the database. Two types of auditing records are maintained: 1. Every record in e..."

New page

All changes made to the data in the software are audited and the audit log is maintained in the database.

Two types of auditing records are maintained:

1. Every record in every table of the database maintains six items of information: created by, created date and time, updated by, updated date and time, deleted by and deleted date and time. Please note that deletions made within the software are not deleted from the database, but are marked as "deleted." Known as a “soft delete,” the software treats the "deleted" records as if they do not exist, except for auditing purposes. Maintaining the created, updated and deleted fields satisfies the majority of auditing requirements.

2. An audit log maintained in a separate database table maintains:

* The creation, update and deletion information
* A record of each field value as it is updated
* A record of the previous value before the update
* The computer date and time
* The database server's date and time
* The computer name
* The logged on user

This log is necessary for review when there is a dispute related to who updated what specific field in a record. This log can become rather large over time and does require periodic purging to a text file.

The system makes the majority of changes to the data as it gets the punches from the time clock, creates the punch information and schedules, and then applies the punches to calculate the time cards, hours and exceptions. It is not practical to maintain an audit log of every change made in this process, because the database would grow to an excessive size within a few days.

The majority of the audit information that is maintained is through the actions of the users of the software, as they perform the following types of actions:

* Logging In
* Logging Out
* Adding or editing employees
* Adding, editing or deleting punches, hours, schedules and placeholders
* Adding or editing the configuration items, e.g. Pay Rules, Base Schedules

← Older revision		Revision as of 04:12, 18 May 2015
Line 1:		Line 1:
−	Changes made ~~in the software~~ are audited ~~with the~~ audit data ~~itself~~ maintained in the database in dedicated columns in every table and a dedicated ~~auditing~~ table.	+	Changes made by users are fully audited. The audit data is maintained within the database through the use of dedicated columns in every table, and a dedicated audit table.

	Two types of auditing records are maintained:		Two types of auditing records are maintained:

@@ Line 1: / Line 1: @@
-All changes made to the data in the software are audited and the audit log is maintained in the database.
+Changes made in the software are audited with the audit data itself maintained in the database in dedicated columns in every table and a dedicated auditing table.
 Two types of auditing records are maintained:
-. Every record in every table of the database maintains six items of information: created by, created date and time, updated by, updated date and time, deleted by and deleted date and time. Please note that deletions made within the software are not deleted from the database, but are marked as "deleted." Known as a “soft delete,” the software treats the "deleted" records as if they do not exist, except for auditing purposes. Maintaining the created, updated and deleted fields satisfies the majority of auditing requirements.
+. Every record in every table of the database maintains six items of information: created by, created date and time, updated by, updated date and time, deleted by and deleted date and time. Additionally, the software used a "soft delete" mechanism where the software treats deleted records as if they do not exist, except for auditing purposes. Maintaining the created, updated and deleted fields allows the quick pinpointing of when a record was created, updated or deleted, but it does not give specifics of what was changed.
 . An audit log maintained in a separate database table maintains:
@@ Line 16: / Line 16: @@
 * The software's user
-This log is necessary for review when there is a dispute related to who updated what specific field in a record. This log can become rather large over time and does require periodic purging to a text file, which can be reloaded back into the software if you need historical auditing information.
+This log gives user specific information down to the individual column in the database. This log can become large over time and does require periodic purging, but can be reloaded back into the software if you need historical auditing information from previous years.
 The system itself makes the majority of changes to the data as it gets punches from the time clock, creates the time cards and schedules, and calculates the time cards creating hours and exceptions. It is not practical to maintain an audit log of every change made in this process, because the database would grow to an excessive size within a few days.

@@ Line 16: / Line 16: @@
 * The software's user
-This log is necessary for review when there is a dispute related to who updated what specific field in a record. This log can become rather large over time and does require periodic purging to a text file, which can be reloaded back into the software if you need historical auditing infomration.
+This log is necessary for review when there is a dispute related to who updated what specific field in a record. This log can become rather large over time and does require periodic purging to a text file, which can be reloaded back into the software if you need historical auditing information.
 The system itself makes the majority of changes to the data as it gets punches from the time clock, creates the time cards and schedules, and calculates the time cards creating hours and exceptions. It is not practical to maintain an audit log of every change made in this process, because the database would grow to an excessive size within a few days.

← Older revision		Revision as of 05:18, 10 May 2015
Line 31:		Line 31:

	* [[Audit Reports]]		* [[Audit Reports]]
		+	* [[Software\|Using the Time and Attendance software]]
		+	* [[Employees]]
		+	* [[Employee]]
		+	* [[Reports]]
		+	* [[Scheduler]]
		+	* [[Tools]]
		+	* [[Configuration]]

@@ Line 22: / Line 22: @@
 The majority of the audit information that is maintained is through the actions of the users of the software, as they perform the following types of actions:
-* Logging In
+* [[Login|Logging In]]
 * Logging Out
 * [[Employees#Add Employees|Adding or editing employees]]

@@ Line 24: / Line 24: @@
 * Logging In
 * Logging Out
-* Adding or editing employees
+* [[Employees#Add Employees|Adding or editing employees]]
 * Adding, editing or deleting punches, hours, schedules and placeholders
 * Adding or editing the configuration items, e.g. changing a pay rules

@@ Line 13: / Line 13: @@
 * The database server's date and time
 * The computer name
-* The logged on user
+* The computer's logged in user
-This log is necessary for review when there is a dispute related to who updated what specific field in a record. This log can become rather large over time and does require periodic purging to a text file.
+This log is necessary for review when there is a dispute related to who updated what specific field in a record. This log can become rather large over time and does require periodic purging to a text file, which can be reloaded back into the software if you need historical auditing infomration.
-The system makes the majority of changes to the data as it gets the punches from the time clock, creates the punch information and schedules, and then applies the punches to calculate the time cards, hours and exceptions. It is not practical to maintain an audit log of every change made in this process, because the database would grow to an excessive size within a few days.
+The system itself makes the majority of changes to the data as it gets punches from the time clock, creates the time cards and schedules, and calculates the time cards creating hours and exceptions. It is not practical to maintain an audit log of every change made in this process, because the database would grow to an excessive size within a few days.
 The majority of the audit information that is maintained is through the actions of the users of the software, as they perform the following types of actions:
@@ Line 25: / Line 26: @@
 * Adding or editing employees
 * Adding, editing or deleting punches, hours, schedules and placeholders
-* Adding or editing the configuration items, e.g. Pay Rules, Base Schedules
+* Adding or editing the configuration items, e.g. changing a pay rules