User:Tule-hog/Volatility (computing)
 | Draft article not currently submitted for review.
This is a draft Articles for creation (AfC) submission. It is not currently pending review. While there are no deadlines, abandoned drafts may be deleted after six months. To edit the draft click on the "Edit" tab at the top of the window. To be accepted, a draft should:
It is strongly discouraged to write about yourself, your business or employer. If you do so, you must declare it. This draft has not been edited in over six months and qualifies to be deleted per CSD G13.
Where to get help
How to improve a draft
You can also browse Wikipedia:Featured articles and Wikipedia:Good articles to find examples of Wikipedia's best writing on topics similar to your proposed article. Improving your odds of a speedy review To improve your odds of a faster review, tag your draft with relevant WikiProject tags using the button below. This will let reviewers know a new draft has been submitted in their area of interest. For instance, if you wrote about a female astronomer, you would want to add the Biography, Astronomy, and Women scientists tags. Editor resources
Last edited by Tule-hog (talk | contribs) 7 months ago. (Update) |
 | This is a draft article. It is a work in progress open to editing by anyone. Please ensure core content policies are met before publishing it as a live Wikipedia article. Last edited by Tule-hog (talk | contribs) 7 months ago. (Update) |
 | Join in and help expand this draft! |
A simple definition of volatility is any "storage media that require an external power supply to maintain stored information."[1] More generally, volatility "measures how quickly data disappears from a system."[2] Contemporary information storage technologies encompass a wide range of volatility characteristics (i.e., time preserved, garbage collection procedures, recoverability). Storage technologies can be ranked according to their volatility by aggregating these characteristics; this ranking is sometimes referred to as the order of volatility.
Order of volatility
RFC 3227 suggests the following order of volatility (from most volatile to least):[3]
- registers, cache
- routing table, arp cache, process table, kernel statistics, memory
- temporary file systems
- disk
- remote logging and monitoring data that is relevant to the system in question
- physical configuration, network topology
- archival media
See also
- Volatile memory, Non-volatile memory
- Computer forensics § Volatile data
- Computer data storage § Volatility
- Computer memory § Volatility categories
- Memory hierarchy - ranking storage based on response time
- Computer data storage § Hierarchy of storage - ranking storage based on distance to CPU
- Digital forensics
References
- ^ R. Shirey (August 2007). Internet Security Glossary, Version 2. Network Working Group. doi:10.17487/RFC4949. RFC 4949. Informational. Obsoletes RFC 2828.
- ^ Jens-Petter Sandvik; Katrin Franke; Habtamu Abie; André Årnes (April 2022). "Quantifying data volatility for IoT forensics with examples from Contiki OS". Forensic Science International: Digital Investigation. 40 (Supplement). doi:10.1016/j.fsidi.2022.301343.
- ^ Brezinski, D.; Killalea, T. (February 2002). Guidelines for Evidence Collection and Archiving. Network Working Group. doi:10.17487/RFC3227. BCP 55. RFC 3227. Best Current Practice 55.
Further reading
- "Chapter 15 - Collecting and Preserving Digital Evidence". Scene of the Cybercrime (2 ed.). Elsevier. 2008. doi:10.1016/B978-1-59749-276-8.X0001-5.