Media-aware by design
The method follows the media.
SectorWipe supports sanitization workflows for NVMe, SATA and SAS SSDs, SATA and SAS HDDs, eMMC, and removable media including USB and CompactFlash—without pretending every device or controller behaves the same way.
Storage media explorer
Different hardware. One honest decision model.
Available methods and assurance depend on the drive, firmware, adapter or controller, health, access path, and the organization’s policy.
PCIe-attached flash
Native capabilities, not an overwrite assumption.
SectorWipe evaluates the NVMe device, firmware-reported capabilities, health, namespace context, and policy before presenting an available sanitization plan.
- Controller-reported capabilities
- Namespace and health context
- Method-appropriate validation
Solid-state media
Flash behavior changes the assurance question.
For SATA and SAS SSDs, the platform considers the media, interface, controller path, supported commands, known restrictions, and required policy outcome.
- SATA and SAS interfaces
- Controller and bridge awareness
- Recorded method rationale
Rotational media
Visible capacity is only part of the drive story.
SectorWipe evaluates rotational drives in context, including interface behavior, reported geometry, health, protected areas, available methods, and verification requirements.
- SATA and SAS transport
- Health and capacity context
- Explicit verification coverage
Embedded storage
Embedded does not mean invisible.
SectorWipe can bring eMMC into the same controlled workflow when the system, firmware, access path, and policy support an acceptable software method.
- Embedded-media identification
- Capability-aware planning
- Refusal when assurance is insufficient
Removable media
The adapter path stays part of the evidence.
USB drives, CompactFlash, and other removable media can be evaluated without pretending every enclosure, bridge, reader, or device exposes the same behavior.
- USB and CompactFlash workflows
- Bridge and reader context
- Honest reduced-assurance outcomes
Before authorization
SectorWipe asks the questions the media requires.
- 01
Media
Flash, rotational, embedded, and removable storage do not expose identical behavior.
- 02
Interface
NVMe, SATA, SAS, and removable-media paths expose different commands and context.
- 03
Controller
Adapters, bridges, readers, and RAID paths can change what the software can observe or request.
- 04
Health
Unreadable regions, firmware state, and reported device health affect the achievable outcome.
- 05
Policy
The required Clear, Purge, or downstream destruction outcome determines what is acceptable.
An honest support boundary
Supported family does not mean universal behavior.
A named media family is not a promise that every model, firmware revision, bridge, RAID controller, reader, or failure state exposes an acceptable software method.
When SectorWipe cannot meet the required outcome, it can refuse the operation or recommend a downstream physical-destruction disposition. That limitation stays visible.
Bring a representative hardware list
Test the edge cases before they become exceptions.
We’ll review drive families, controllers, adapters, policy requirements, connectivity, and the evidence your operation needs.