Seagate Secure archive

Seagate Exos SED and FIPS Model List: Standard, ISE and Secure Variants

“Seagate Secure” is not one universal feature applied to every Exos drive. Standard, instant-secure-erase, self-encrypting and FIPS-oriented variants use different exact model numbers and can require different host, controller or management support. This page organizes verified and representative records by exact model, while marking configurations that still require manual confirmation. It also explains why a seller’s “encrypted” label does not prove active locking, compliance or a clean ownership state.

Use the exact-model tool Compare Exos prices

Select the security class from the requirement, then verify the exact model and management path

Choose standard storage when no managed encryption is required, ISE when rapid cryptographic sanitization is the goal, SED when authentication and locking will be managed, and a validated FIPS variant only when formal policy requires it. Buying a secure-capable drive without the management system does not automatically secure data.

Security warning: SED capability does not automatically enable locking, and an SED is not automatically a FIPS-validated model.

Interactive decision tool

Standard, ISE, SED or FIPS requirement selector

Exact-model archive

Specialist models must not inherit ordinary Exos specifications

Use the complete model number to confirm family, capacity, interface, sector format, security class, recording technology and actuator count. Ambiguous records remain marked for verification rather than being silently mapped to a similar suffix.

Exact model	Family	Capacity	Interface	Sector	Security	Recording / actuators
ST2400MM0139	Exos 10E2400	2.4TB	SAS	512e / 4Kn model-dependent	ISE / verify exact configuration	CMR · 1 actuator
ST2400MM0149	Exos 10E2400	2.4TB	SAS	512e / 4Kn model-dependent	SED or FIPS variant — verify	CMR · 1 actuator
ST600MM0218	Exos 10E2400	600GB	SAS	512n	SED	CMR · 1 actuator
ST12000NM0017	Exos X12	12TB	SATA	512e	SED	CMR · 1 actuator
ST12000NM0037	Exos X12	12TB	SAS	512e / 4Kn	SED	CMR · 1 actuator
ST12000NM001H	Exos X24	12TB	SATA	512e / 4Kn FastFormat	SED	CMR · 1 actuator
ST12000NM005H	Exos X24	12TB	SAS	512e / 4Kn model-dependent	SED	CMR · 1 actuator
ST12000NM009H	Exos X24	12TB	SAS	512e / 4Kn model-dependent	SED-FIPS	CMR · 1 actuator
ST16000NM001H	Exos X24	16TB	SATA	512e / 4Kn FastFormat	SED	CMR · 1 actuator
ST16000NM005H	Exos X24	16TB	SAS	512e / 4Kn model-dependent	SED	CMR · 1 actuator
ST16000NM006H	Exos X24	16TB	SAS	512e / 4Kn model-dependent	SED-FIPS	CMR · 1 actuator
ST20000NM001H	Exos X24	20TB	SATA	512e / 4Kn FastFormat	SED	CMR · 1 actuator

Standard models do not inherit secure-drive claims

A standard Exos drive can provide enterprise storage and ordinary erase workflows, but it should not be advertised as an SED or FIPS device. Retail titles often copy family-level features across variations. Cloudzat stores standard and secure exact models separately and only displays a security class when the model record supports it.

ISE focuses on rapid sanitization

Instant Secure Erase generally uses internal encryption so that changing or destroying the media key can make existing data unreadable quickly. ISE does not necessarily provide user-managed locking or authentication in the same way as an SED. It is valuable for decommissioning, but the exact command, tool and organizational procedure must be documented.

SED adds managed authentication capability

A self-encrypting drive can support locking and authentication through a compatible management environment. Hardware capability alone does not mean the drive is currently locked. The host, controller and security software must support the relevant standard. Recovery keys, ownership transfer and failure procedures need to be planned before deployment.

FIPS is a specific compliance claim

A FIPS-oriented model should be selected only when the exact drive and configuration meet the required validation and organizational policy. A generic SED, ISE model or encrypted-data claim is not a substitute. Verify the exact model, certification scope, firmware and management stack with the compliance owner rather than relying on an Amazon title.

Exact X12 secure models

The X12 support list clearly separates ST12000NM0017 SED SATA and ST12000NM0037 SED SAS from their standard counterparts. This demonstrates why suffixes matter. The same capacity and generation can have different interface and security characteristics. Model-level identity must be preserved through purchasing, inventory and replacement.

X24 secure variants span SATA and SAS

X24 includes separate SED and SED-FIPS records across capacities, with different SATA and SAS exact models. The interface, sector format and security class should be verified together. Do not assume that every secure variant supports the same sector conversion, controller or firmware path as a standard channel model.

Management software and controller visibility

Some RAID controllers virtualize drives and can hide security commands. Appliance NAS firmware may not expose SED management even when the physical drive contains encryption hardware. Confirm that the full path from management software to drive supports discovery, ownership, locking, unlocking, erase and recovery. Test before production deployment.

Used SED ownership can be a serious risk

A used SED can arrive locked, with an unknown credential, or sanitized into a state the buyer does not understand. Ask the seller to confirm that security ownership has been removed and the drive is accessible in an ordinary supported host. A low price is not useful if the device cannot be unlocked or returned.

Cryptographic erase is not a backup

Secure erase destroys access to data; it does not preserve it. Verify backups, legal holds and retention requirements before sanitization. Maintain stable power and use an approved tool. Do not use a security erase as a troubleshooting experiment on a drive containing required data.

Security does not replace physical and operational controls

Drive encryption is one layer. Systems still require access control, key custody, monitoring, backups, secure boot, network protection and documented disposal. A failed encrypted drive can also complicate recovery if keys or management metadata are lost. Security architecture should include failure and personnel-change scenarios. Before disposal, verify that the organization can prove which sanitization method was used, who authorized it and whether the device remained under custody. Compliance evidence should reference the exact model and serial, not only the storage array name. Where policy requires physical destruction, cryptographic erase may be one step rather than the final disposition.

Marketplace verification rules

Require the exact model in the selected variation, not just the description. Compare interface, capacity, sector format and security class. Reject listings that call ISE FIPS, claim SED without a matching model, or mix new and recertified condition. Record seller and warranty source because secure OEM inventory can follow a different support route. Managed encryption creates an operational dependency on credentials, recovery keys and the management platform. Store recovery material under controlled procedures and test authorized recovery before production data accumulates. Personnel changes, controller replacement and disaster recovery should not make a healthy drive inaccessible. A secure design includes both protection against unauthorized access and a reliable path for authorized restoration.

Selection workflow

Start with the policy requirement: ordinary storage, fast sanitization, managed locking or formal FIPS compliance. Confirm the host and management system. Select exact models that match interface, sector and capacity. Verify seller, condition, ownership state and warranty. Document keys and decommissioning before data is written, not after the drive is retired. Record exact model, serial, firmware, interface, sector format, security class and warranty source at receiving. Apply asset tags that do not cover the factory label. Keep standard and secure spares in separate inventory bins, because a visually similar model can create a failed replacement or compliance exception. Procurement should prohibit model substitution without technical and security approval.

Current exact-model offers

Verify the specialist model before purchase

No fresh verified exact-model offers are stored for this page yet. Initialize and refresh the specialist catalogue from the plugin admin screen.

Find This Model on Amazon

Exos authority cluster

Seagate Exos authority hub Current Exos exact-model list Exos SATA vs SAS Exos 512e vs 4Kn Current Exos prices Seagate Exos 7E10 Model List: SATA, SAS, 512n, 512e and 4Kn Seagate Exos 10E2400: 2.5-Inch 10K SAS Model and Replacement Guide Seagate Exos 2X18 MACH.2: Dual-Actuator Compatibility and Buying Guide Seagate Exos Xz SMR: Host-Managed Zoned Storage Compatibility Guide Seagate Exos X12: Models, SATA vs SAS, SED and Buying Guide

Frequently asked questions

Specialist and legacy Exos answers

Is every Exos drive self-encrypting?

No. Standard, ISE, SED and FIPS variants use different exact model numbers.

What is the difference between ISE and SED?

ISE primarily supports rapid cryptographic sanitization, while SED adds managed authentication and locking capabilities.

Does SED mean the drive is automatically locked?

No. The host and management software must configure and manage the security features.

Is every SED FIPS certified?

No. FIPS is a separate exact-model and certification requirement.

Can a consumer NAS manage an Exos SED?

Only if the appliance explicitly supports the relevant security commands and management workflow.

Can I use an SED as a normal drive?

Often yes when it is unlocked and no locking policy is enabled, but exact behavior and ownership state must be verified.

Is cryptographic erase reversible?

It is intended to make prior data inaccessible. Treat it as destructive and verify backups and retention requirements first.

Should I buy a used SED?

Only when the seller confirms it is unlocked, ownership is cleared, the exact model is documented and a return path exists.

Do SATA and SAS secure models use the same management path?

Not necessarily. Controller, protocol and software support can differ.

How should I choose a secure Exos model?

Begin with the security policy, then match exact model, interface, sector format, host management and warranty source.

Official references

Cloudzat may earn a commission from qualifying purchases. Confirm the exact model, controller, sector format, recording architecture, security state, warranty and platform compatibility before purchase.