Fact-checked by Grok 2 weeks ago

Write protection

Write protection is a in that prevents the writing, modification, or of on devices, ensuring and protecting against accidental or unauthorized alterations. This feature is implemented through hardware or software methods to render read-only while allowing to be read and accessed. Hardware write protection typically involves physical components, such as toggle switches on USB flash drives or SD cards, which mechanically block write operations when activated. In contrast, software write protection uses operating system controls, file permissions, or specialized commands—for example, the diskpart utility in Windows or [hdparm](/page/Hdparm) in —to enforce read-only status on drives or partitions. Key mechanisms include hardware write blockers, which intercept and nullify write commands at the interface level (e.g., via , , or protocols), and software-based filters that modify system interrupts or driver behaviors to prevent data changes. These approaches are applied to various media, including hard disk drives, solid-state drives, optical discs like CDs and DVDs (which can be finalized to prevent further writing), and removable storage like floppy disks with protective tabs. Write protection plays a critical role in by mitigating risks from , human error, or deliberate tampering, and it is especially vital in , where and software blockers ensure preservation during acquisition without altering original , maintaining chain-of-custody for . Benefits extend to compliance with standards in industries handling sensitive information, such as healthcare and , where unaltered records are essential.

Fundamentals

Definition

Write protection is a safeguard in that prevents from being modified, overwritten, or deleted on media or files. This feature ensures the of stored information by restricting write operations while permitting read . At its core, write protection operates on the principle of enforcing read-only , which distinguishes between read operations—allowing retrieval—and write operations—blocking any alterations. This enforcement can occur at the level through physical components or at the software level via operating system commands and . The technical scope of write protection encompasses both physical storage media, such as disks and , and digital files within file systems. It includes intentional forms, where users activate protection manually, and automatic forms, where systems enforce it to maintain data stability. The terminology "write protection" originated in the context of early systems during the 1950s, driven by the need to prevent accidental erasure on devices like reels, which used a removable ring to enable or disable writing.

Purpose

Write protection serves primarily to prevent accidental data loss by safeguarding storage media against unintended modifications or deletions, thereby maintaining the accuracy and availability of stored information. This is particularly crucial in scenarios where , such as overwriting critical files, could lead to significant disruptions; for instance, accidental deletions account for a substantial portion of incidents, contributing to broader human-error-related breaches, with the human element involved in 68% of breaches analyzed in the 2024 Verizon DBIR. By enforcing immutability on data, write protection also shields against or unauthorized alterations, reducing the risk of infection or tampering that could compromise system integrity. In terms of risk mitigation, write protection addresses vulnerabilities like hardware failures during write operations, which might otherwise corrupt , as well as intentional threats such as tampering. It preserves original for essential purposes like backups and archives, ensuring tamper-proof copies that support reliable recovery and forensic analysis without fear of alteration. These measures are vital in environments prone to errors, where industry reports indicate that factors, including unintended writes, drive up to 95% of data breaches in some sectors. On a broader scale, write protection enhances data reliability across workflows by minimizing downtime from , aids compliance with retention policies through immutable storage solutions like (WORM) technologies, and yields cost savings by averting expensive recovery efforts—potentially billions annually in breach-related losses tied to preventable errors.

Mechanisms

Hardware Methods

Hardware methods for write protection involve physical mechanisms embedded directly into storage devices to prevent data modification at the hardware level. These techniques rely on mechanical or electrical components that interrupt write operations independently of software controls. Physical switches provide a simple, user-accessible way to enforce write protection on removable media. On 3.5-inch floppy disks, a sliding tab or notch on the disk's casing serves as the write-protect mechanism; when the tab covers the notch, the disk drive's read/write head cannot record data, as the drive detects the covered position and blocks write signals. Similarly, some USB flash drives incorporate a mechanical read/write protection switch, typically a small slider on the drive's exterior, which alters an electrical signal to the controller, preventing write access across all capacities. Firmware-level controls extend write protection to solid-state drives (SSDs) and hard disk drives (HDDs) through built-in read-only modes. In SSDs, a physical switch or on the board connects to a (GPIO) pin, which the monitors to activate a locking that prohibits writes, deletions, or formatting. For HDDs and SSDs, settings or dedicated pins on the drive or can enable read-only configurations, where the intercepts and rejects write commands at the device level. At the circuitry level, write protection operates by interrupting write signals within the storage controller. The controller receives data commands via interfaces like USB or ; a protection switch or pin grounds or alters a dedicated signal line (e.g., a write-enable pin), causing the controller's logic gates to block the write path while allowing read operations to proceed. This ensures writes are halted before reaching the medium. Despite their effectiveness, methods have limitations related to physical accessibility. Switches on devices like floppy disks or USB drives can be easily toggled or bypassed by an attacker with physical access, such as by repositioning the tab or shorting the protection circuit. In non-secure , such as consumer-grade SSDs without tamper-evident , firmware-level protections via jumpers may also be disabled through direct board , underscoring the need for additional physical safeguards.

Software Methods

Software methods for write protection involve operating system-level and programmatic techniques that enforce restrictions on modifying files or volumes without relying on physical . These approaches leverage metadata, mount options, and application programming interfaces () to designate data as read-only, allowing dynamic control that can be applied or reversed as needed. Such methods are integral to , enabling users and administrators to safeguard data against accidental or unauthorized alterations. File system attributes provide a foundational way to implement write protection at the individual file or directory level. In the file system used by Windows, the read-only attribute (FILE_ATTRIBUTE_READONLY) prevents modifications to a file's contents, though it does not restrict renaming or deletion unless combined with other permissions. This attribute can be set using command-line tools or , ensuring that applications attempting to write to the file receive an access denied error. Similarly, the file system employs an ATTR_READ_ONLY flag in the directory entry, which signals to the operating system that any write or delete operations on the file should be rejected, a feature dating back to early implementations. In Unix-like systems such as with , write protection is achieved through permission bits, where the write bit (w) is cleared for owner, group, and others—typically via the command with modes like (read-only for all) or symbolic notation such as a-w file to remove write permissions universally. These attributes operate at the level, integrating with the file system's model to enforce immutability. At the volume level, software methods extend protection to entire storage partitions or devices. In , the command supports the (read-only) option, which attaches a in a mode that prohibits all writes, replaying the if necessary but preventing subsequent modifications to ensure during maintenance or auditing. For example, mounting with mount -o /dev/sda1 /mnt safeguards the volume against changes until remounted with rw (read-write). In Windows, volumes can be set to read-only using the diskpart utility with the command attributes volume set readonly, which applies the protection across the entire partition, including or volumes, and is particularly useful for forensic imaging or temporary safeguards. While tools like primarily focus on , they can integrate with these mount options to create protected, read-only views of encrypted volumes in policy-enforced environments. These volume-level techniques are reversible and do not require hardware intervention, making them suitable for scripted automation. API integrations allow developers to enforce write protection programmatically within applications. In Windows, the SetFileAttributes function from the Win32 sets the FILE_ATTRIBUTE_READONLY flag on a specified or directory, returning a success indicator and integrating seamlessly with I/O operations to block writes at the level. For systems, the chmod(2) modifies mode bits to remove write permissions, accepting an octal mode like 0444 and updating the inode atomically to prevent concurrent modifications. These enable fine-grained control, such as toggling protection based on user roles or application state, and are commonly used in or systems to maintain . Advanced software features build on these basics to provide more robust protection mechanisms. In Oracle Solaris' implementation of the ZFS file system, immutable files can be created using the chmod S+ci command, which sets the system immutable flag (S_IMMUTABLE), preventing any modifications, deletions, or even renaming until the flag is cleared—even by root privileges—offering strong safeguards against malware or operator error. On Linux implementations of ZFS, the chattr +i command achieves similar immutability. ZFS snapshots further enhance this by creating read-only, point-in-time copies of entire file systems or volumes that consume minimal initial space through copy-on-write semantics, allowing safe browsing and recovery without altering the original data. Similarly, BTRFS supports read-only snapshots via the btrfs subvolume snapshot command with the -r flag, producing immutable views that serve as the foundation for incremental backups and versioned storage, where changes to the parent volume do not affect the snapshot. In version control systems like Git, snapshot-based read-only views are realized through commits, which represent frozen states of the repository that cannot be altered directly; checking out a commit provides a detached, read-only working tree unless branched, facilitating historical analysis and rollback without risking current work. These features prioritize data durability and are widely adopted in enterprise storage and development workflows.

Applications

Consumer and Everyday Use

Write protection plays a crucial role in everyday by safeguarding on removable and portable devices against accidental or unauthorized modifications. In consumer settings, it allows non-technical users to preserve files such as family photos, work documents, or backups without needing advanced software configurations. Common implementations focus on simplicity, often integrating physical switches or automated features to prevent overwrites during routine tasks like file transfers or device sharing. Removable media frequently incorporates straightforward hardware mechanisms for write protection. USB flash drives from manufacturers like Kingston and often feature a small sliding lock switch on the casing, which, when engaged, renders the drive read-only and prevents any data writing or deletion until unlocked. Similarly, SD cards used in digital cameras and smartphones include a physical write-protect notch on the side; sliding the tab to the "lock" position blocks modifications, a design standardized by the to protect media during sessions or transfers. These features are particularly useful for consumers transporting files, as they provide an immediate, tool-free way to maintain without relying on computer settings. Built-in device features extend write protection to integrated storage in personal electronics. Smartphones running or operating systems enforce read-only status on system partitions by default, using file system attributes to prevent user-level alterations to core software files, thereby protecting against or erroneous updates during daily app usage. External hard disk drives (HDDs), such as those from or Seagate, commonly include software-based write protection via bundled , allowing users to secure entire volumes, such as through password locking, before connecting to another computer. These automated safeguards simplify protection for backups, ensuring that critical files remain unaltered even if the device is handled by others. In typical user workflows, write protection supports practical scenarios like securing vacation photos on memory cards to avoid overwrites when reviewing them on a home computer, or enabling it on a USB drive containing backed-up documents before lending it to a colleague for viewing only. For instance, photographers often lock SD cards immediately after a shoot to preserve raw images during editing sessions, preventing accidental deletions amid file imports. Backing up financial records to an external HDD with software protection similarly allows safe sharing with accountants without risking edits, integrating seamlessly into routines like monthly data archiving. Such applications highlight how write protection fits into casual data management, reducing the need for constant vigilance. Accessibility remains a key consideration for non-technical users, with physical switches on USB drives and SD cards praised for their intuitive design that requires no menus or commands, making them ideal for seniors or casual users handling family media. However, common pitfalls include forgetting to engage the switch before transporting a device, leading to unintended if the drive is inserted into an unfamiliar , or overlooking software-based overrides on computers that might ignore locks in certain configurations. To mitigate these, manufacturers recommend verifying protection status via simple checks, such as attempting to save a test file, ensuring broad without steep learning curves.

Forensic and Professional Use

In digital forensics and professional investigations, write blockers serve as essential hardware devices that enable the safe acquisition and examination of storage media by preventing any write operations to the original . These tools create a one-way read-only interface, ensuring that data cannot be altered, deleted, or appended during analysis, which is critical for maintaining evidentiary integrity. Prominent examples include the Tableau line of write blockers, which support multiple interfaces such as USB, , and PCIe for connecting various drive types, and WiebeTech models like the Forensic UltraDock, designed for forensically sound access to bare hard drives in investigative settings. The National Institute of Standards and Technology (NIST) rigorously tests these devices through its Tool Testing (CFTT) program to verify their blocking efficacy across different operating systems and configurations. Write protection plays a pivotal role in upholding of custody for , which documents the handling of materials from to presentation in to demonstrate that no unauthorized changes occurred. By employing write blockers, forensic examiners prevent accidental or intentional modifications that could compromise the evidence's authenticity, thereby supporting its admissibility under legal standards that require proof of unaltered preservation. For instance, failure to use such protections during can lead to challenges in , as alterations—even minor ones like changes—may render unreliable or excluded. This process ensures a verifiable , aligning with requirements in proceedings where digital artifacts like files or logs must remain in their original state. In enterprise and professional environments, specialized software tools integrate write-blocking capabilities to facilitate comprehensive digital investigations. Forensic, developed by , incorporates hardware write-blocker recommendations and supports the creation of bit-for-bit images while enforcing read-only access to source media, allowing analysts to perform timeline analysis and keyword searches without risking evidence tampering. Similarly, FTK Imager from Exterro provides free imaging functionality that works in tandem with hardware write blockers to produce verifiable duplicates, often using hash verification to confirm integrity during the forensic imaging process. These tools are widely adopted in and corporate incident response for their ability to handle large-scale data sets securely. Compliance with established standards further reinforces the use of write protection in professional handling. The NIST Special Publication series, including IR 8387 on Preservation, outlines procedures for acquisition that emphasize write-blocking to avoid alterations and ensure in forensic workflows. Likewise, ISO/IEC 27037:2012 provides international guidelines for the identification, collection, acquisition, and preservation of , explicitly recommending write protection mechanisms to mitigate risks during the initial handling phases and support interoperability across jurisdictions. Adherence to these standards helps professionals demonstrate in maintaining evidence reliability for legal and audit purposes.

History and Evolution

Early Developments

The origins of write protection emerged in the mid-20th century alongside the development of technologies, primarily to safeguard valuable data on expensive media in nascent systems. In the 1950s, pioneered as a key storage medium for mainframe computers, replacing cumbersome punched cards and enabling faster . The IBM 726 tape drive, announced in 1952 as part of the system, marked an early milestone in tape storage. Building on this, the IBM 729 tape drive, introduced in 1953, featured a mechanical write protection mechanism consisting of a removable ring inserted into a circular groove on the back of the 1/2-inch tape reel. When the ring was present, the drive allowed writing; its removal rendered the tape read-only, preventing accidental overwrites during operations like data backup or program loading. This design was crucial in early environments where tapes cost hundreds of dollars and errors could halt critical tasks, such as scientific calculations or business accounting. In the 1980s, write protection for optical media evolved with the introduction of compact discs (). The CD standard, developed by and and released in 1982, included a finalization process that closed sessions on write-once (CD-R), rendering them read-only to prevent further alterations. This mechanism ensured for audio and data distribution.) Building on tape-based protections, write mechanisms evolved with the shift to more portable in the 1970s. IBM's development of the began in 1971 under engineer , who led the creation of an 8-inch flexible disk prototype for loading into /370 mainframes, initially as a read-only medium to avoid altering core system instructions. By 1973, IBM commercialized the first read-write version with the 33FD drive in the 3740 , incorporating a write-protect notch on the disk's edge—a small cutout detected by a mechanical sensor in the drive. Covering the notch with enabled writing, while leaving it open enforced read-only mode, addressing the need to protect office computing data from inadvertent changes during and transfer tasks. This innovation stemmed from the era's motivations to mitigate risks in shared computing setups, where magnetic media was prone to corruption from human error or hardware faults, and tapes or disks represented significant investments. Key milestones in the 1970s and 1980s further standardized these features for broader adoption. Shugart, after leaving , founded in 1973, which refined the 8-inch floppy interface and produced compatible drives that popularized the write-protect notch in minicomputer systems. By the early 1980s, with the PC's launch in 1981, PC DOS version 1.0 integrated support for 5.25-inch floppies, enforcing read-only access when the protect mechanism was engaged to prevent filesystem alterations during or . These developments reflected the era's emphasis on data reliability in cost-sensitive environments, where overwriting irreplaceable records could disrupt emerging personal and business computing workflows.

Modern Advancements

In the , the proliferation of in portable storage devices like USB drives introduced electronic write protection mechanisms to prevent unauthorized modifications, often implemented through firmware-based locks that could be toggled via software or hardware interfaces without physical switches. These features addressed the vulnerabilities of early flash storage, where was crucial for data transfer in professional environments. Advancing into the 2010s, self-encrypting drives (SEDs) emerged as a significant innovation, integrating hardware-based encryption with write protection under the Trusted Computing Group (TCG) Opal standard, first specified in 2009 and widely adopted by 2010. The Opal specification enables drives to automatically encrypt data at rest using AES algorithms, with built-in authentication to control write access, reducing the performance overhead of software encryption and enhancing security for enterprise storage. Toshiba, for instance, released SEDs compliant with Opal in 2010, marking a shift toward standardized, scalable protection in hard disk drives and solid-state drives. By the mid-2010s, Opal 2.0 further refined these capabilities, supporting multi-user access controls and FIPS 140-2 validation, which became essential for compliance in data centers. Cloud storage platforms in the 2010s adopted write-once-read-many (WORM) models to provide virtualized write protection, particularly for archival and compliance needs, with (AWS) introducing S3 Glacier Vault Lock in 2016 to enforce immutable retention periods. This was followed by S3 Object Lock in 2018, which applies WORM semantics to objects in S3 buckets, preventing deletions or overwrites for specified durations in either governance or modes. These features ensure data immutability at scale, allowing organizations to store petabytes of information securely, as demonstrated by regulated industries using S3 Glacier for long-term retention without risking tampering. In the 2020s, and have driven proactive write protection by automating detection and response to threats like , which often targets modifiable storage. Microsoft's cloud-based system, deployed since 2021, analyzes device behavior in real-time to predict risks and dynamically apply protective measures, such as isolating affected storage volumes to block writes. Similarly, tools from providers like leverage ML algorithms with up to 85% accuracy in identifying anomalous file encryption patterns, enabling automated enforcement of read-only states on endpoints. Google Workspace introduced AI-powered detection in Drive for desktop in 2025, which pauses syncing and applies temporary write locks upon detecting mass file modifications. These advancements represent a toward predictive, self-healing storage protection. Regulatory frameworks post-2010, including the EU's (GDPR) effective 2018 and updates to the U.S. Portability and Accountability Act (HIPAA), have accelerated the adoption of immutable storage features to safeguard integrity. GDPR's emphasis on data protection by design (Article 25) and accountability requires mechanisms to prevent unauthorized alterations, spurring WORM implementations in cloud services to maintain audit trails for breach reporting within 72 hours. HIPAA's Security Rule, reinforced through 2013 omnibus updates and ongoing guidance, mandates safeguards for electronic (ePHI), including immutable retention to ensure records remain unaltered for at least six years, as supported by WORM-compliant storage solutions. These regulations have influenced vendors to integrate advanced immutability, such as retention locks in AWS S3, directly addressing compliance risks in healthcare and finance.

References

  1. [1]
    How Does Write-Protect Work? Exploring Storage Device Security | Lenovo US
    ### Summary of Write-Protect from Lenovo Glossary
  2. [2]
    What Is Write Protection - ITU Online IT Training
    Write protection is a feature that prevents data from being altered or erased on a storage device. This safeguard can be implemented through hardware or.Missing: credible sources
  3. [3]
    [PDF] Computer Forensic Functions Testing: Media Preparation, Write ...
    Accordingly, two types of write protection techniques are developed, that are hardware write protection. (blocking) and software write protection (blocking).<|control11|><|separator|>
  4. [4]
    Hardware Write Blocker - an overview | ScienceDirect Topics
    In the context of Computer Science, hardware write-blockers provide read-only access to digital storage media and prevent inadvertent or malicious modification ...
  5. [5]
    WRITE-PROTECT definition | Cambridge English Dictionary
    to protect the data on a computer disk so that it cannot be changed or removed by a user: Many operating systems include a command to write-protect files. write ...Missing: storage | Show results with:storage<|separator|>
  6. [6]
    The Life of a Data Byte - Communications of the ACM
    Dec 1, 2020 · A removable plastic ring on the back of the tape reel provided write protection. ... Data is recorded when a magnetic write-head flies just above ...
  7. [7]
    The Data Loss Survey: Over 70% of ... - Handy Recovery Advisor
    Rating 4.6 (11) Jul 7, 2025 · Over 70% of users have lost data at least once. · Accidental deletion (34%) and hardware failure (30%) cause most data loss. · Nearly 60% of users ...
  8. [8]
    [PDF] 2024 Data Breach Investigations Report | Verizon
    May 5, 2024 · For this year's dataset, the human element was a component of 68% of breaches, roughly the same as the previous period described in the 2023 ...
  9. [9]
    How to Turn Write Protection on or Off for a USB Flash Drive
    Sep 12, 2023 · The write protection switch is useful for keeping the contents of your drive safe from malware when you must view them on a public computer. If ...
  10. [10]
    [PDF] Data Integrity: Identifying and Protecting Assets Against ...
    ▫ Secure storage allows data storage with additional data protection measures, such as Write. Once Read Many (WORM) technologies. Data encryption can also ...
  11. [11]
    95% of Data Breaches Tied to Human Error in 2024
    Mar 11, 2025 · Human error contributed to 95% of data breaches in 2024, driven by insider threats, credential misuse and user-driven errors, according to a new study by ...
  12. [12]
    Machine-Readable Media | National Archives
    May 2, 2023 · Do not attempt to reposition the write-protect switch on floppy disks.. Avoid marking on the media; label the container whenever possible. If ...
  13. [13]
    [PDF] 1.44MB 3.5” FLOPPY DISK IMAGING MANUAL
    Aug 23, 2018 · ▸. Connect directly to the computer USB input. ▸. Switch the floppy disk write-block tab to the correct position. ▹. It may be helpful to do ...
  14. [14]
    [PDF] USB Flash Drives Overview - University of Utah - Mac Managers
    - Read/Write protection switch. - Available on all capacities. -. -. - Basic password protection. - Available on all capacities. USB Flash Drives - Basic ...<|separator|>
  15. [15]
    Write Protection - UDinfo
    UDinfo SSD "write protection" is designed to protect data integrity. It's a locking mechanism which avoids modification of data on a storage device.
  16. [16]
    Information and Support for Serial ATA, EIDE Drive Jumper Settings
    Aug 20, 2018 · Run CMOS Setup and configure the BIOS to see the drives. Check the system or motherboard for instructions. View the Use of Third-Party ...
  17. [17]
    How reliable is a write protection switch on a USB flash drive?
    Jun 1, 2011 · Overall, a USB based write protection switch is extremely reliable as long as it is fully hardware based or utilizes a combination of hardware and software ...Missing: benefits | Show results with:benefits
  18. [18]
    File Attribute Constants (WinNT.h) - Win32 apps | Microsoft Learn
    Sep 23, 2025 · These constants allow developers to check and set file properties such as read-only, hidden, or compressed attributes. For a list of related ...
  19. [19]
    SetFileAttributesA function (fileapi.h) - Win32 apps - Microsoft Learn
    Jun 1, 2023 · Sets the attributes for a file or directory. To perform this operation as a transacted operation, use the SetFileAttributesTransacted function.Syntax · Parameters
  20. [20]
    FAT Filesystem - Elm-chan.org
    Flag, Meaning. ATTR_READ_ONLY, Read-only File. Any changes to the file or delete should be rejected. ATTR_HIDDEN, Normal directoly listing should not show this ...Basics of FAT File System · Association of File and Cluster · Long File Name
  21. [21]
    mount(8) - Linux manual page - man7.org
    The mount command automatically canonicalizes all paths (from the command line or fstab). This option can be used in conjunction with the -f flag for paths that ...
  22. [22]
    chmod(2) - Linux manual page - man7.org
    The chmod() and fchmod() system calls change a file's mode bits. (The file mode consists of the file permission bits plus the set- user-ID, set-group-ID, and ...Synopsis Top · Description Top · Errors Top
  23. [23]
    Applying Immutability to a ZFS File - Oracle Help Center
    Use the following syntax to make a file immutable: Copy $ chmod S+ci file.1 $ echo this >>file.1 -bash: file.1: Insufficient privileges $ rm file.1
  24. [24]
    Overview of ZFS Snapshots
    A snapshot is a read-only copy of a file system or volume. Snapshots can be created almost instantly, and they initially consume no additional disk space within ...
  25. [25]
    btrfs-subvolume(8) - BTRFS documentation!
    Read-only snapshots are building blocks of incremental send (see btrfs-send(8)) and the whole use case relies on unmodified snapshots where the relative changes ...
  26. [26]
    Hardware Write Block | NIST
    Test Results (Federated Testing) for Hardware Write Block Device WiebeTech Forensic ComboDock v6 (June 2022) ... Write Block Tool -Tableau Forensic SAS Bridge ...
  27. [27]
    [PDF] Digital Evidence and the U.S. Criminal Justice System
    As part of the authentication process, chain of custody assures that digital evidence has been preserved in its original form. This entails being able to ...
  28. [28]
    Breaking the Chain: Common Mistakes in Digital Evidence Handling
    Jan 13, 2025 · Failing to use write protection devices or software when acquiring data from digital media can render evidence inadmissible. In many cases, ...
  29. [29]
    [PDF] Understanding Digital Forensic Tools: Their Features, Applicability ...
    EnCase recommends using write-blocking hardware during evidence collection. This ensures that no changes can be made to the original media, further safeguarding ...
  30. [30]
    [PDF] Digital Evidence Preservation - NIST Technical Series Publications
    Sep 18, 2022 · The FSRP directs research efforts to develop performance standards, measurement tools, operating procedures, guidelines, and reports that will ...
  31. [31]
    ISO/IEC 27037:2012 - Information technology — Security techniques
    In stockISO/IEC 27037:2012 provides guidelines for specific activities in the handling of digital evidence, which are identification, collection, acquisition and ...
  32. [32]
    Magnetic tape | IBM
    Beginning in the early 1950s, magnetic tape greatly increased the speed of data processing and eliminated the need for massive stacks of punched cards as a data ...
  33. [33]
    IBM Mainframe Magnetic Storage Media - Columbia University
    If the tape was mounted with a write-ring, the user could write on the tape; otherwise it was read-only. The operator would insert the ring according to the ...
  34. [34]
    1971: Floppy disk loads mainframe computer data
    IBM shipped the first units of Noble's solution, the 23 FD “Minnow” in 1971. The 8-inch floppy disk drive with removable read-only, flexible "memory disks” ...Missing: notch | Show results with:notch
  35. [35]
    Floppy disk storage - IBM
    IBM began selling floppy disk drives in 1971 and received US patents for the drive and floppy disk in 1972. The floppy disk made it possible to easily load ...Missing: notch | Show results with:notch
  36. [36]
    DOS 1.0 and 1.1 | OS/2 Museum
    DOS 1.0 could read and write 160KB floppy disks, start .COM and .EXE applications, and process batch (.BAT) files. It could keep track of date and time.
  37. [37]
    USB flash drive write protection | TechSpot Forums
    Dec 29, 2004 · I've two EasyDisk flash sticks with the write protect problem. It doesn't matter which position the switch is in it still comes up as write protected.Missing: electronic | Show results with:electronic
  38. [38]
    Kanguru's Secure USB Memory Stick - Tom's Hardware
    Aug 21, 2008 · The Kanguru Defender series of USB flash sticks was developed for professional use. The housing consists of robust aluminum, which makes the ...
  39. [39]
    [PDF] The Era of Self-Encrypting Drives (SEDs) - Trusted Computing Group
    Jan 5, 2010 · Self-Encrypting Drives are non-volatile storage devices that encrypt the data received through the interface before writing to the non- ...
  40. [40]
    Toshiba Announces Self-Encrypting Drive Designed to Trusted ...
    Nov 30, 2010 · SEDs designed to the Opal SSC specification provide advanced access authentication and built-in hardware data encryption. Because it is an open ...
  41. [41]
    Self encryption drive supported by TCG-opal 2.0 - ATP Electronics
    Jul 25, 2019 · Self-encrypting drives (SEDs) supporting Opal 2.0 use hardware encryption technology to secure data stored in them.Missing: 2010s | Show results with:2010s
  42. [42]
    Your All-in-One Guide to Self-Encrypting Drives (SEDs)
    Oct 13, 2020 · SEDs conforming to TCG Opal 2.0 use 128-bit block sizes with 128-bit and 256-bit AES keys. The latter two numbers refer to the actual key ...Missing: 2010s | Show results with:2010s
  43. [43]
    Protecting backup archives with WORM and Tape Retention Lock
    Aug 19, 2020 · Tape Gateway already supports WORM capability on the virtual tapes that are archived in AWS. Virtual tapes archived in Amazon S3 Glacier or S3 ...Protecting Backup Archives... · Overview · What Is Tape Retention Lock?
  44. [44]
    Protecting data with Amazon S3 Object Lock | AWS Storage Blog
    Sep 5, 2019 · Many AWS customers use AWS' WORM storage capabilities (S3 Glacier Vault Lock and S3 Object Lock) today. A regulated broker-dealer uses the WORM ...
  45. [45]
    Amazon S3 Glacier storage classes
    Amazon S3 Object Lock enables WORM storage capabilities, helping satisfy compliance requirements for virtually every regulatory agency around the globe.Amazon S3 Glacier Storage... · Benefits · How It Works: S3 Glacier...
  46. [46]
    The Role of AI and ML in Ransomware Protection - Acronis
    Jun 27, 2023 · According to the IBM Security X-Force report, machine learning algorithms have an 85% accuracy rate in detecting ransomware attacks by ...
  47. [47]
    AI-driven adaptive protection against human-operated ransomware
    Nov 15, 2021 · We developed a cloud-based machine learning system that, when queried by a device, intelligently predicts if it is at risk, then automatically issues a more ...
  48. [48]
    Block ransomware proliferation and easily restore files with AI in ...
    Sep 30, 2025 · Google Drive for desktop now features AI-powered ransomware detection to automatically pause syncing and enable fast, ...Missing: write 2020s
  49. [49]
    Worm Storage Immutability Regulatory Compliance | Grotabyte Blog
    Sep 18, 2025 · These technologies provide the foundation for defensible archiving that meets strict regulatory requirements such as SEC 17a-4, FINRA, HIPAA, ...
  50. [50]
    Understanding Immutable Storage: The Backbone of Data Resilience
    Mar 12, 2025 · Immutable storage guarantees that data remains unaltered, helping organizations meet compliance requirements for HIPAA, GDPR, and SEC ...
  51. [51]
    Understanding WORM Compliance: What is WORM Storage & Why ...
    Healthcare providers must meet HIPAA requirements to securely store patient records. WORM storage ensures these records are tamper-proof and retained for ...
  52. [52]
    Your guide to WORM Compliant Storage - Global Relay
    May 23, 2024 · What are the WORM compliant storage requirements? · Only allow data to be written in once · Prevent any user from deleting the data · Keep records ...