The IT Law Wiki
(Created page with "== Definition == '''Integrity checking''' tools can detect whether any critical system files have been changed, thus enabling the system administrator to look for [[unau…")
 
m
Tag: Source edit
 
(4 intermediate revisions by 2 users not shown)
Line 1: Line 1:
 
== Definition ==
 
== Definition ==
   
  +
'''Integrity checking''' is
'''Integrity checking''' tools can detect whether any critical [[system file]]s have been changed, thus enabling the [[system administrator]] to look for [[unauthorized]] [[alteration]] of the [[system]].
 
  +
  +
{{Quote|[t]he [[testing]] of [[program]]s to [[verify]] the soundness of a [[software]] product at each phase of development.<ref>[[Auditing and Financial Management: Glossary of EDP Terminology]], at 9.</ref>}}
   
 
== Overview ==
 
== Overview ==
   
 
Integrity checking tools can detect whether any critical [[system file]]s have been changed, thus enabling the [[system administrator]] to look for [[unauthorized]] [[alteration]] of the [[system]].
Integrity checkers examine [[stored]] [[file]]s or [[network packet]]s to determine if they have been [[altered]] or changed. These checkers are based on [[checksum]]s &mdash; a simple mathematical operation that turns an entire [[file]] or a [[message]] into a number. More complex [[hash function]]s that result in a fixed string of [[encrypted data]] are also used. The integrity checking process begins with the creation of a baseline, where [[checksum]]s or [[hash]]es for clean [[data]] are [[compute]]d and saved. Each time the integrity checker is run, it again makes a [[checksum]] or [[hash]] computation and compares the result with the [[stored value]].
 
  +
[[Category:Technology]]
 
  +
Integrity checkers examine [[stored]] [[file]]s or [[network packet]]s to determine if they have been [[altered]] or changed. They can only flag a change as suspicious; they cannot determine if the change is a genuine [[virus]] [[infection]].
  +
 
These checkers are based on [[checksum]]s &mdash; a simple mathematical operation that turns an entire [[file]] or a [[message]] into a number. More complex [[hash function]]s that result in a fixed string of [[encrypted data]] are also used. The integrity checking process begins with the creation of a baseline, where [[checksum]]s or [[hash]]es for clean [[data]] are [[compute]]d and saved. Each time the integrity checker is run, it again makes a [[checksum]] or [[hash]] computation and compares the result with the [[stored value]].
  +
  +
== References ==
  +
<references />
  +
 
[[Category:Software]]
 
[[Category:Data]]
 
[[Category:Data]]
 
[[Category:Security]]
 
[[Category:Security]]

Latest revision as of 00:04, 13 October 2021

Definition[]

Integrity checking is

[t]he testing of programs to verify the soundness of a software product at each phase of development.[1]

Overview[]

Integrity checking tools can detect whether any critical system files have been changed, thus enabling the system administrator to look for unauthorized alteration of the system.

Integrity checkers examine stored files or network packets to determine if they have been altered or changed. They can only flag a change as suspicious; they cannot determine if the change is a genuine virus infection.

These checkers are based on checksums — a simple mathematical operation that turns an entire file or a message into a number. More complex hash functions that result in a fixed string of encrypted data are also used. The integrity checking process begins with the creation of a baseline, where checksums or hashes for clean data are computed and saved. Each time the integrity checker is run, it again makes a checksum or hash computation and compares the result with the stored value.

References[]