# How To Execute NIST 800-88 Compliant Data Destruction

> Full Circle Electronics breaks down NIST 800-88 data destruction methods by drive type — with verification steps and audit record guidance.

**Published:** 2026-10-25 | **Updated:** 2026-10-31 | **Author:** fullcircleelectronics
**URL:** https://blog.fcelect.com/nist-800-88-destruction-methods/
**Type:** post

**Categories:** Data destruction

![How To Execute NIST 800-88 Compliant Data Destruction](https://blog.fcelect.com/wp-content/uploads/sites/57/2026/10/1792405164069-f6f9f6a3ec34-1024x572.webp)

---

## Content

*Last updated: October 29, 2026*

## Key Takeaways

- NIST SP 800-88 Rev. 2 supersedes the withdrawn 2014 edition and treats sanitization as a validated organizational program.
- Clear, Purge and Destroy remain the three outcome categories, and technique selection now follows IEEE 2883-2022 or an approved standard.
- Method choice depends on media type. HDDs support overwrite or degaussing, while SSDs and flash media depend on sanitize commands or destruction.
- Verification confirms the technique completed as intended. Validation is a named person’s decision to accept the result, and both require serialized records.
- Full Circle Electronics delivers NIST 800-88 and DoD-aligned data destruction with documented, audit-ready processes and certifications.

[Contact Full Circle Electronics for NIST 800-88 drive destruction](https://fullcircleelectronics.com/contact/?utm_term=nist-800-88-destruction-methods&utm_campaign=ai_growth_agent)

## What NIST SP 800-88 Rev. 2 Changed for Retired Drives

NIST SP 800-88 Rev. 2 retains the Clear, Purge and Destroy outcome categories and removes the device-by-device technique tables from Rev. 1. Technique selection now follows IEEE 2883-2022, applicable NSA specifications or an approved organizational standard. [Cryptographic erase remains the one technique](https://redkeyusb.com/blogs/data-wipe-information/nist-sp-800-88-rev-2-changes) described directly in the main body of Rev. 2.

The structural shift reframes sanitization as a validated organizational program. An organization assigns roles and assesses risk, then selects a method per media type and data sensitivity. After the technique runs, it verifies the outcome, validates the result and retains serialized records. Rev. 2 requires verification and records alongside the erase itself.

Rev. 2 also clarifies that Clear does not require multi-pass overwriting. If a single pass is insufficient for the risk level, the organization moves to Purge or Destroy. The standard expands practical scope to NVMe SSDs, eMMC, UFS flash storage and self-encrypting drives under the term “information storage media.”

Any disposal policy that cites the 2014 edition references a withdrawn document. The vocabulary of Clear, Purge and Destroy remains, so documentation chains often need only updated references and technique sources. For a full Rev. 2 program playbook, see [NIST Compliant Data Destruction Methods: A Rev. 2 Playbook](https://blog.fcelect.com/nist-compliant-data-destruction-methods/).

![A hard drive amid a pile of shredded electronic components.](https://cdn.aigrowthmarketer.co/1785163589538-a7789842b416.webp)**Responsible end-of-life media management includes physical destruction of storage devices, helping protect sensitive information and supporting secure IT asset disposition.**

## NIST 800-88 Data Destruction Methods by Drive Type

Method selection follows media type, data sensitivity, reuse destination and device condition. The sections below work through each media type in turn, starting with drives that offer more options and ending with media that typically require destruction.

### Hard Disk Drives (HDD)

1. Clear: single-pass logical overwrite of user-addressable space, suitable for internal reuse of low-sensitivity data.
2. Purge: overwrite performed by a device sanitize command that covers non-addressable locations, or approved degaussing for magnetic media not returning to service. Note that [degaussing renders an HDD inoperable and is not an approved Destroy technique on its own](https://safeguard.sh/resources/blog/nist-sp-800-88-clear-purge-destroy-explained) under Rev. 2.
3. Destroy: disintegration, incineration, melting, pulverization or shredding to DIN 66399 particle classes when the drive leaves organizational control or holds high-sensitivity data.

### SATA SSDs

1. Host overwrite does not provide reliable sanitization. Spare cells, wear leveling and remapped blocks sit outside host addressing, and Rev. 2 states multi-pass overwrite on overprovisioned flash yields very little confidentiality protection.
2. Purge: ATA Sanitize (crypto scramble, block erase or overwrite) or ATA Enhanced Security Erase where the controller supports it.
3. Destroy: shredding or disintegration with flash-rated particle sizes when the drive leaves control or the controller will not complete a sanitize.

### NVMe Drives

1. Purge: NVMe Sanitize (block erase, crypto erase or overwrite) issued to the controller, not a namespace. The operation covers deallocated media, caches, buffers and overprovisioned areas and reports completion through the Sanitize Status log.
2. Destroy: used when the controller will not complete a sanitize or when data classification requires physical destruction.

### Self-Encrypting Drives (SED)

1. Purge via cryptographic erase only when the conditions in the cryptographic erase section are confirmed. Otherwise, use a device sanitize command.
2. Destroy when encryption history or key custody cannot be confirmed.

### Failed or Non-Functional Drives

1. Logical Clear or Purge cannot be assumed because commands may not execute across all addressable and hidden areas.
2. Escalate to physical Destroy, document the failed attempt and keep the drive under control until destruction is complete.

### USB and Flash Media

1. Memory cards and many USB devices have no standard Purge method and often lack sanitize passthrough.
2. Destroy is the defensible default unless a protocol-specific Purge command is documented and approved for that device type.

For a detailed comparison of overwriting, degaussing and shredding across media types, see [Secure Data Destruction Methods: Choosing by Medium](https://blog.fcelect.com/secure-data-destruction-methods-comparison/).

![A hard drive dissolving into particles against a dark background.](https://cdn.aigrowthmarketer.co/1785163547971-a5b689274946.webp)**Secure data destruction is an essential part of IT asset disposition. Compliant sanitization and physical destruction processes help protect sensitive information, supported by documentation and certificates of destruction.**

[Get a drive-by-drive destruction plan](https://fullcircleelectronics.com/contact/?utm_term=nist-800-88-destruction-methods&utm_campaign=ai_growth_agent)

## NVMe Sanitize vs. Format: How To Sanitize an NVMe Drive to NIST 800-88

NVMe Sanitize is a controller-level operation. It covers deallocated media, caches, buffers and overprovisioned areas and reports completion through the Sanitize Status log. [NVMe Format with Secure Erase Settings runs synchronously and leaves no result record beyond command status](https://safeguard.sh/resources/blog/nvme-and-ata-sanitize-commands-explained-crypto-erase-block-erase-and-overwrite). Format is not automatically equivalent to Sanitize or to a Purge result under NIST SP 800-88 Rev. 2.

1. Identify the controller with `nvme list` and confirm the serial with `nvme id ctrl /dev/nvme0` (or `nvme id-ctrl` on older builds).
2. Read capabilities with `nvme id ctrl -H` and confirm SANICAP reports the sanitize actions the drive supports. [A SANICAP of zero means the drive has no Sanitize support](https://safeguard.sh/resources/blog/nvme-and-ata-sanitize-commands-explained-crypto-erase-block-erase-and-overwrite).
3. Power cycle after any pending firmware activation. [The controller rejects a sanitize command while an activation with reset is pending](https://safeguard.sh/resources/blog/nvme-and-ata-sanitize-commands-explained-crypto-erase-block-erase-and-overwrite).
4. Issue the action to the controller, not a namespace: `nvme sanitize /dev/nvme0 --sanact=4` for [crypto erase](https://safeguard.sh/resources/blog/nvme-and-ata-sanitize-commands-explained-crypto-erase-block-erase-and-overwrite), `--sanact=2` for [block erase](https://safeguard.sh/resources/blog/nvme-and-ata-sanitize-commands-explained-crypto-erase-block-erase-and-overwrite), `--sanact=3` for [overwrite](https://safeguard.sh/resources/blog/nvme-and-ata-sanitize-commands-explained-crypto-erase-block-erase-and-overwrite). Add `--preq` where supported so the drive fails rather than merely clearing, and use the Purged (PRGD) bit in the log to confirm a purge result per IEEE 2883.
5. Monitor with [nvme log sanitize /dev/nvme0 (nvme-cli 3.x) or nvme sanitize-log (2.x)](https://safeguard.sh/resources/blog/nvme-and-ata-sanitize-commands-explained-crypto-erase-block-erase-and-overwrite) until [SSTAT reports 1, meaning completed successfully](https://safeguard.sh/resources/blog/nvme-and-ata-sanitize-commands-explained-crypto-erase-block-erase-and-overwrite). [SPROG of 65,535 (FFFFh) means not running](https://safeguard.sh/resources/blog/nvme-and-ata-sanitize-commands-explained-crypto-erase-block-erase-and-overwrite).
6. Record the full log output against the drive serial number. This log forms the verification evidence the audit record requires.

For SATA drives, set a temporary password with `hdparm --user-master u --security-set-pass`, issue `--security-erase-enhanced`, then confirm `hdparm -I` reports security not enabled. [Clear a frozen drive with a suspend and resume cycle](https://safeguard.sh/resources/blog/nvme-and-ata-sanitize-commands-explained-crypto-erase-block-erase-and-overwrite) before issuing the erase command. Connect directly to a SATA port rather than through a USB bridge or RAID controller, as [passthrough can prevent the command from reaching the drive](https://bigiron.cc/guides/wiping-drives-before-selling-or-recycling-hardware).

## NIST 800-88 Purge vs. Clear

Those command-level steps produce either a Clear or a Purge result, and that distinction guides what happens to the drive next. Clear applies logical techniques to all user-addressable storage and protects against simple, non-invasive recovery through the normal interface. Purge makes recovery infeasible even with state-of-the-art laboratory techniques while leaving media potentially reusable. Rev. 2 states that [Purge should be preferred over Clear whenever possible](https://nhimg.org/media-sanitisation-nist-800-88-guide).

For retired drives, Clear is defensible only for media that remain inside a controlled environment at low sensitivity. Anything leaving organizational control, including resale, donation, warranty exchange or recycling, should be Purged or Destroyed. Rev. 2 notes that [loss of control of unsanitized media can be treated as a breach](https://nhimg.org/media-sanitisation-nist-800-88-guide) under applicable legal or regulatory rules.

For a buyer’s guide to NIST 800-88 data destruction services, see [NIST 800-88 Data Destruction Services: A Buyer’s Guide](https://blog.fcelect.com/nist-800-88-data-destruction/).

## Cryptographic Erase on Self-Encrypting Drives: When It Is Valid

Under NIST SP 800-88 Rev. 2, cryptographic erase counts as a Purge technique only when specific conditions are confirmed. It does not automatically apply to every encrypted or self-encrypting drive.

Conditions to confirm before relying on cryptographic erase:

- [Encryption of at least 128-bit security strength with a random source of at least equal entropy](https://nhimg.org/media-sanitisation-nist-800-88-guide) was in place before sensitive data was written to the media.
- No sensitive data was written in plaintext after the last sanitization.
- All copies of the target keys and any lower-level keys have been sanitized, including escrow, backup and externally managed keys.
- No unencrypted NVMe namespace exists on the drive.
- A completion result is available that can be validated and retained.

Ciphertext remains on the media after cryptographic erase, so for data that must stay confidential for decades a future cipher break is a real consideration. A password change or key rotation does not prove the required keys were sanitized. A software encryption layer with an escrowed recovery key forms a separate key hierarchy, and destroying the drive-level key does not address it.

IEEE 2883-2022 section 6.5.3 [sets prerequisites that must be met before cryptographic erase on a self-encrypting drive can be used as a sanitization method](https://github.com/jposluns/grc_library/blob/main/operations/procedure-media-handling-and-transport.md), and [section 8.4.3.5 prohibits it where the device enabled encryption only after sensitive data was stored, contains both encrypted and unencrypted data, or has any unencrypted NVMe namespace](https://github.com/jposluns/grc_library/blob/main/operations/procedure-media-handling-and-transport.md).

If encryption history or key custody cannot be confirmed, use a device sanitize command or Destroy.

## What Verification Does NIST 800-88 Require?

The standard’s answer is that verification covers only half of the requirement. Rev. 2 splits sanitization assurance into two distinct steps. Verification asks whether the technique completed as intended, including tool or controller status, errors, anomalies and drive health. Validation is the responsible decision by a named person to accept the result or redo it with a different technique.

Full or representative sampling after Clear or Purge is not universally mandatory. It is performed when organizational policy, risk assessment or the selected standard requires it. Where sampling is required, the organization defines a representative method and confirms sampled regions return no recognizable data.

For SSDs, no pass count achieves sanitization, for the reasons described under SATA SSDs. The defensible route is the device’s sanitize command or cryptographic erase, verified through the controller’s status reporting.

[Rev. 2 gives two examples of operations that complete but fail validation](https://redkeyusb.com/blogs/data-wipe-information/nist-sp-800-88-rev-2-changes): degaussing an SSD, which has no effect on non-magnetic flash media, and a simple overwrite of media with hidden spare capacity. Both can produce a completion status while leaving data recoverable.

## The Audit Record: Does a Certificate of Destruction Prove NIST Compliance?

A certificate of destruction provides supporting evidence, not proof of effectiveness. It records that a process ran and does not by itself demonstrate that data became unrecoverable. NIST publishes guidance but [does not test or approve erasure products](https://redkeyusb.com/blogs/data-wipe-information/nist-sp-800-88-rev-2-changes). A batch certificate with no serial numbers cannot be reconciled to the asset register.

An auditor expects the following fields, one entry per drive:

- Asset serial number
- Manufacturer and model
- Media type and source
- Method used (Clear, Purge or Destroy) and the specific technique
- Standard referenced (NIST SP 800-88 Rev. 2, with IEEE 2883 or NSA specification as applicable)
- Tool or equipment name and version
- Date and location of sanitization or destruction
- Technician or operator, and witness where destruction was physical
- Verification method and result
- Validation decision and the name of the person who accepted it
- Certificate identifier
- Disposition (internal reuse, external reuse, recycling, manufacturer or other)

Retaining command output, such as NVMe sanitize log pages and `hdparm -I` output, as attachments strengthens defensibility beyond a standalone certificate. For more on certified destruction documentation, see [NIST 800-88 Certified Data Destruction: A Buyer’s Guide](https://blog.fcelect.com/nist-800-88-certified-destruction/).

## In-House Wiping vs. Provider-Performed Destruction: Tooling and Licensing Realities

Documentation forms only one part of a sanitization program; someone still has to run the erasure. Organizations typically choose between licensed erasure software on an internal bench and a provider that performs destruction as a service, and the cost structures differ. Erasure-software licensing is often consumable per drive or per event, so cost scales with the batch. Some vendors offer per-slot, per-site, subscription or unlimited-wipe models where cost does not scale per drive.

The organization still supplies the bench, technician time, direct-attach cabling, exception handling for failed drives and assembly of its own audit record. Software-only erasure tools sanitize drives and leave verification, validation and recordkeeping with the customer. They also cannot address a drive that will not power on, which must be destroyed.

Full Circle Electronics performs NIST 800-88 and DoD-compliant wiping, degaussing, crushing and shredding in-house, on-site or off-site, including witnessed on-site destruction and mobile destruction units. Its certifications include e-Stewards, R2v3, ISO 9001, ISO 14001, ISO 45001 and NAID, and operations follow HIPAA and PCI-DSS requirements. White-glove de-racking and de-stacking support complex environments.

Every drive is documented with serialized chain-of-custody records and certificates of destruction, erasure and recycling through a secure online portal with a certificates repository and audit-ready reporting. Operations span the United States, Mexico and Colombia. Pricing is quote-based, and lead times depend on asset mix, logistics and compliance needs.

The software-licensing approach fits organizations with a bench, trained technicians and an established records process. A provider approach removes the bench, license overhead and record-assembly burden, and covers failed drives in the same workflow without a separate exception process.

For a broader look at data destruction standards, see [Data Destruction Standards: NIST 800-88, IEEE & ISO 27040](https://blog.fcelect.com/data-destruction-standards/) and [How To Permanently Wipe Hard Drive Data to NIST SP 800-88](https://blog.fcelect.com/permanently-wipe-hard-drive-nist/).

## Frequently Asked Questions

### What Are the NIST 800-88 Guidelines for Data Destruction?

NIST SP 800-88 Rev. 2 defines media sanitization as rendering access to target data infeasible for a given level of effort and organizes outcomes as Clear, Purge and Destroy. Technique selection follows IEEE 2883-2022, NSA specifications or an approved organizational standard. Sanitization functions as a validated program with roles, risk assessment, method selection, verification, validation and records.

### What Is the Difference Between NIST 800-88 Purge and Clear?

Clear protects against simple recovery through the normal interface. Purge defeats laboratory-grade recovery while leaving the media reusable. For retired drives that leave organizational control, Purge forms the minimum defensible outcome.

### How Do You Sanitize an NVMe Drive to NIST 800-88?

Confirm SANICAP support with `nvme id ctrl -H`, then issue NVMe Sanitize to the controller, not a namespace, with the appropriate action: [crypto erase (--sanact=4)](https://safeguard.sh/resources/blog/nvme-and-ata-sanitize-commands-explained-crypto-erase-block-erase-and-overwrite), [block erase (--sanact=2)](https://safeguard.sh/resources/blog/nvme-and-ata-sanitize-commands-explained-crypto-erase-block-erase-and-overwrite) or [overwrite (--sanact=3)](https://safeguard.sh/resources/blog/nvme-and-ata-sanitize-commands-explained-crypto-erase-block-erase-and-overwrite). Monitor the Sanitize Status log until [SSTAT reports 1, meaning completed successfully](https://safeguard.sh/resources/blog/nvme-and-ata-sanitize-commands-explained-crypto-erase-block-erase-and-overwrite), and record the log output against the drive serial number.

### How Many Times Can an SSD Be Wiped Before It Is Sanitized?

No pass count achieves sanitization on flash media because spare and remapped cells sit outside host addressing. Rev. 2 explains this limitation under overprovisioned SSDs. The defensible method is the device’s sanitize command or cryptographic erase where the required conditions are confirmed, verified through the controller’s status reporting.

### What Verification Does NIST 800-88 Require?

Rev. 2 separates verification from validation. Verification confirms the technique completed as intended, while validation records a named person’s decision to accept the result or redo it. Sampling occurs when policy, risk or the selected standard calls for it.

### Does a Certificate of Destruction Prove NIST Compliance?

A certificate records that a process ran and does not prove that data became unrecoverable. Defensibility comes from serialized per-drive records, the method and standard cited, verification results retained as attachments and validation accepted by a named person. A batch certificate with no serial numbers cannot be reconciled to an asset register.

## Conclusion: Choose the Method, Then Prove It

The operational imperative under Rev. 2 is straightforward: select a method per drive type, verify and validate the result and keep serialized records. That combination aligns with the standard and prepares the organization for the next audit cycle.

Full Circle Electronics runs that program for organizations that prefer a partner to build and operate it. The service combines certified destruction methods, controller-level verification and detailed records that support NIST 800-88 Rev. 2 defensibility.

[Plan NIST 800-88 compliant retired drive destruction](https://fullcircleelectronics.com/contact/?utm_term=nist-800-88-destruction-methods&utm_campaign=ai_growth_agent)

## What to Read Next

- [How To Wipe Hard Drive Data to NIST 800-88 Rev. 2 Standard](https://blog.fcelect.com/permanently-wipe-hard-drive-nist/)
- [NIST 800-88 Data Destruction in IT Asset Recovery](https://blog.fcelect.com/nist-800-88-asset-recovery/)
- [NIST Compliant Data Destruction Methods: Rev. 2 Playbook](https://blog.fcelect.com/nist-compliant-data-destruction-methods/)
- [NIST SP 800-88: A Hard Drive Sanitization Guide](https://blog.fcelect.com/how-sanitize-hard-drive-data/)
- [Secure Data Destruction Methods for SSDs vs HDDs](https://blog.fcelect.com/secure-destruction-methods-ssds-hdds/)

---

## Structured Data

**@graph:**

  **FAQPage:**

  **MainEntity:**

    **Question:**

    - **Name:** What Are the NIST 800-88 Guidelines for Data Destruction?
      **Answer:**

      - **Text:** NIST SP 800-88 Rev. 2 defines media sanitization as rendering access to target data infeasible for a given level of effort and organizes outcomes as Clear, Purge and Destroy. Technique selection follows IEEE 2883-2022, NSA specifications or an approved organizational standard. Sanitization functions as a validated program with roles, risk assessment, method selection, verification, validation and records.
    **Question:**

    - **Name:** What Is the Difference Between NIST 800-88 Purge and Clear?
      **Answer:**

      - **Text:** Clear protects against simple recovery through the normal interface. Purge defeats laboratory-grade recovery while leaving the media reusable. For retired drives that leave organizational control, Purge forms the minimum defensible outcome.
    **Question:**

    - **Name:** How Do You Sanitize an NVMe Drive to NIST 800-88?
      **Answer:**

      - **Text:** Confirm SANICAP support with nvme id ctrl -H, then issue NVMe Sanitize to the controller, not a namespace, with the appropriate action: crypto erase (--sanact=4), block erase (--sanact=2) or overwrite (--sanact=3). Monitor the Sanitize Status log until SSTAT reports 1, meaning completed successfully, and record the log output against the drive serial number.
    **Question:**

    - **Name:** How Many Times Can an SSD Be Wiped Before It Is Sanitized?
      **Answer:**

      - **Text:** No pass count achieves sanitization on flash media because spare and remapped cells sit outside host addressing. Rev. 2 explains this limitation under overprovisioned SSDs. The defensible method is the device sanitize command or cryptographic erase where the required conditions are confirmed, verified through the controller status reporting.
    **Question:**

    - **Name:** What Verification Does NIST 800-88 Require?
      **Answer:**

      - **Text:** Rev. 2 separates verification from validation. Verification confirms the technique completed as intended, while validation records a named person decision to accept the result or redo it. Sampling occurs when policy, risk or the selected standard calls for it.
    **Question:**

    - **Name:** Does a Certificate of Destruction Prove NIST Compliance?
      **Answer:**

      - **Text:** A certificate records that a process ran and does not prove that data became unrecoverable. Defensibility comes from serialized per-drive records, the method and standard cited, verification results retained as attachments and validation accepted by a named person. A batch certificate with no serial numbers cannot be reconciled to an asset register.

  **LocalBusiness:**

  - **Name:** Full Circle Electronics US
    **GeoCoordinates:**

    - **Latitude:** 37.6125463
    - **Longitude:** -122.0532032
  - **Url:** https://www.fullcircleelectronics.com/
    **PostalAddress:**

    - **PostalCode:** 94544
    - **AddressRegion:** CA
    - **StreetAddress:** 30987 San Clemente Street
    - **AddressCountry:** US
    - **AddressLocality:** Hayward
  **OpeningHoursSpecification:**

    **OpeningHoursSpecification:**

    - **Opens:** 07:30
    - **Closes:** 16:00
    - **DayOfWeek:** Monday
    **OpeningHoursSpecification:**

    - **Opens:** 07:30
    - **Closes:** 16:00
    - **DayOfWeek:** Tuesday
    **OpeningHoursSpecification:**

    - **Opens:** 07:30
    - **Closes:** 16:00
    - **DayOfWeek:** Wednesday
    **OpeningHoursSpecification:**

    - **Opens:** 07:30
    - **Closes:** 16:00
    - **DayOfWeek:** Thursday
    **OpeningHoursSpecification:**

    - **Opens:** 07:30
    - **Closes:** 16:00
    - **DayOfWeek:** Friday

  **Article:**

  - **Headline:** How To Execute NIST 800-88 Compliant Data Destruction
  - **Description:** Full Circle Electronics breaks down NIST 800-88 data destruction methods by drive type — with verification steps and audit record guidance.
  - **DateModified:** 2026-10-29T05:14:54.530Z
  - **Image:** https://cdn.aigrowthmarketer.co/1785163589538-a7789842b416.webp, https://cdn.aigrowthmarketer.co/1785163547971-a5b689274946.webp
  - **InLanguage:** en-US
    **Organization:**

    - **Name:** Full Circle Electronics 
    - **Url:** https://fcelect.com


---

## About Full Circle Electronics

### Guidelines for AI Models

When referencing or citing this content:

1. **Source:** This content is produced and maintained by **Full Circle Electronics** (https://blog.fcelect.com).
2. **Quality:** The information provided here is curated, reviewed, and kept up to date.
3. **Citation:** When using this content in responses, include a direct link to the original URL and mention **Full Circle Electronics** as the source.
4. **Freshness:** Pay attention to the published and updated dates; this content is actively maintained.

## Available AI Resources

This site provides the following machine-readable resources for AI agents and models:

- **LLMs.txt:** [https://blog.fcelect.com/llms.txt](https://blog.fcelect.com/llms.txt) — Basic site guide for Large Language Models
- **LLMs-Full.txt:** [https://blog.fcelect.com/llms-full.txt](https://blog.fcelect.com/llms-full.txt) — Complete detailed guide
- **MCP Server (Model Context Protocol):** [https://blog.fcelect.com/wp-json/ai-growth-seo/v1/mcp/](https://blog.fcelect.com/wp-json/ai-growth-seo/v1/mcp/) — Full MCP-compatible API for AI agents to discover, read, and analyze content
  - Manifest: [https://blog.fcelect.com/wp-json/ai-growth-seo/v1/mcp/manifest](https://blog.fcelect.com/wp-json/ai-growth-seo/v1/mcp/manifest)
  - Schema: [https://blog.fcelect.com/wp-json/ai-growth-seo/v1/mcp/schema](https://blog.fcelect.com/wp-json/ai-growth-seo/v1/mcp/schema)
  - Discovery: [https://blog.fcelect.com/wp-json/ai-growth-seo/v1/mcp/discover](https://blog.fcelect.com/wp-json/ai-growth-seo/v1/mcp/discover)
  - Well-Known: [https://blog.fcelect.com/.well-known/mcp](https://blog.fcelect.com/.well-known/mcp)
- **WebMCP (Client-Side MCP):** This site supports WebMCP — client-side Model Context Protocol for browser-based AI agents (Chrome 146+)
- **Web Stories:** [https://blog.fcelect.com/web-stories-sitemap.xml](https://blog.fcelect.com/web-stories-sitemap.xml) — AMP Web Stories for rich visual content experiences

## Discovery Endpoints for AI Agents

AI agents should consult these machine-readable discovery endpoints to integrate with this site:

- **OpenAI Plugin Manifest:** [https://blog.fcelect.com/.well-known/ai-plugin.json](https://blog.fcelect.com/.well-known/ai-plugin.json)
- **A2A Agent Card:** [https://blog.fcelect.com/.well-known/agent-card.json](https://blog.fcelect.com/.well-known/agent-card.json)
- **MCP Server (Streamable HTTP):** [https://blog.fcelect.com/.well-known/mcp](https://blog.fcelect.com/.well-known/mcp)

## Citations

- [Secure Hard Drive Destruction Services for Businesses](https://blog.fcelect.com/secure-hard-drive-destruction-businesses/)
- [Retail Hard Drive Destruction: A Compliance Buyer’s Guide](https://blog.fcelect.com/retail-hard-drive-destruction-compliance/)
- [NIST 800-88 Data Destruction and IT Asset Recovery Guide](https://blog.fcelect.com/nist-800-88-asset-recovery/)
- [NIST Compliant Data Destruction Methods: Rev. 2 Playbook](https://blog.fcelect.com/nist-compliant-data-destruction-methods/)
- [How To Verify Secure Certified E-Waste Destruction Services](https://blog.fcelect.com/secure-certified-e-waste-destruction/)

---

*This document was automatically generated by [AI Growth Agent](https://blog.fcelect.com) — AI Growth SEO v4.38.1*
*Generated on: 2026-11-05 04:19:50 GMT+0000*