{"id":12769,"date":"2025-10-07T16:58:55","date_gmt":"2025-10-07T15:58:55","guid":{"rendered":"https:\/\/www.secure-itad.com\/?p=12769"},"modified":"2026-03-06T17:00:45","modified_gmt":"2026-03-06T17:00:45","slug":"standaarden-voor-gegevensvernietiging-uitgelegd","status":"publish","type":"post","link":"https:\/\/www.secure-itad.com\/nl\/standaarden-voor-gegevensvernietiging-uitgelegd\/","title":{"rendered":"Standaarden voor gegevensvernietiging uitgelegd"},"content":{"rendered":"\n\t<div id=\"text-1851058222\" class=\"text article-underline\">\n\t\t\n\n<h2>The master checklist, decision framework for an audit-ready exit<\/h2>\n<p>Decommissioning a data centre isn\u2019t just a logistics job. It\u2019s a risk event: one missed asset, one untracked handover, or one unclear destruction method can create operational disruption, compliance exposure, and a lot of uncomfortable questions.<\/p>\n<p>This playbook is designed to help you run a decommissioning project with confidence. It breaks the work into clear phases, shows you what \u201cgood\u201d looks like at each step, and ends with a closeout pack you can hand to auditors, security stakeholders, and finance.<\/p>\n<p>If you\u2019d like a Secure ITAD specialist to help you scope the project, build the plan, or deliver the full service end-to-end, you can book a scoping call at the bottom of this page.<\/p>\n\t\t\t<\/div>\n\t\n\t<div id=\"gap-773792464\" class=\"gap-element clearfix\" style=\"display:block; height:auto;\">\n\t\t\n<style>\n#gap-773792464 {\n  padding-top: 30px;\n}\n<\/style>\n\t<\/div>\n\t\n\n<span class=\"scroll-to\" data-label=\"Scroll to: #iso-27001\" data-bullet=\"false\" data-link=\"#iso-27001\" data-title=\"ISO 27001\"><a name=\"iso-27001\"><\/a><\/span>\n\n\t<div id=\"gap-12230667\" class=\"gap-element clearfix\" style=\"display:block; height:auto;\">\n\t\t\n<style>\n#gap-12230667 {\n  padding-top: 30px;\n}\n<\/style>\n\t<\/div>\n\t\n\n\t<div id=\"text-3254813206\" class=\"text article-underline\">\n\t\t\n\n<h2>Who this is for<\/h2>\n<p>This guide is aimed at teams planning one of the following:<\/p>\n<p>A full data centre exit, a partial shutdown or consolidation, a refresh programme in a live environment, or a multi-site decommissioning programme where consistency, chain of custody, and reporting are non-negotiable.<\/p>\n\t\t\t<\/div>\n\t\n\t<div id=\"gap-1817354406\" class=\"gap-element clearfix\" style=\"display:block; height:auto;\">\n\t\t\n<style>\n#gap-1817354406 {\n  padding-top: 30px;\n}\n<\/style>\n\t<\/div>\n\t\n\n\t<div id=\"text-667413457\" class=\"text article-underline\">\n\t\t\n\n<h2>Start here: Define the type of decommission<\/h2>\n<p>Before you touch a rack, get clarity on what you\u2019re actually doing. Most projects fall into one of these categories:<\/p>\n<p>Full exit: everything is removed, processed, and closed out as a single programme.<br \/>Partial decommission: specific rows, pods, or suites are removed while adjacent services remain live.<br \/>Live-environment de-rack: removals are executed under strict change windows and access controls.<br \/>Multi-site programme: consistency is the biggest risk, so governance and reporting need to be standardised.<\/p>\n<p>The most common point of failure is under-scoping. If you\u2019re not explicit about what\u2019s included (and what isn\u2019t), you\u2019ll end up with stranded equipment, incomplete records, or late-stage \u201csurprises\u201d that add time and cost.<\/p>\n\t\t\t<\/div>\n\t\n\t<div id=\"gap-356304731\" class=\"gap-element clearfix\" style=\"display:block; height:auto;\">\n\t\t\n<style>\n#gap-356304731 {\n  padding-top: 30px;\n}\n<\/style>\n\t<\/div>\n\t\n\n\t<div id=\"text-1746150834\" class=\"text article-underline\">\n\t\t\n\n<h2>Phase 0: Governance, timelines and controls<\/h2>\n<p>A decommissioning programme becomes simpler when everyone agrees what \u201cdone\u201d means.<\/p>\n<p>Start by assigning a single owner for delivery (internal project lead or external PM), and make sure your governance covers: change windows, access requirements, safety rules, and escalation paths. If you\u2019re operating in a live environment, define what constitutes \u201cstop work\u201d conditions before day one.<\/p>\n<p>At this stage, build three foundational documents:<\/p>\n<ol>\n<li>A clear scope statement (what is being removed and what stays).<\/li>\n<li>A RACI that makes accountability obvious across IT, facilities, security, compliance and the vendor.<\/li>\n<li>A risk register that is specific to your environment (for example: outage risk, access limitations, asset loss, chain-of-custody breaks, and schedule constraints).<\/li>\n<\/ol>\n<p>When these are in place, you can plan backwards from the shutdown date and create a realistic timeline for discovery, execution, processing, and closeout reporting.<\/p>\n\t\t\t<\/div>\n\t\n\t<div id=\"gap-453540486\" class=\"gap-element clearfix\" style=\"display:block; height:auto;\">\n\t\t\n<style>\n#gap-453540486 {\n  padding-top: 30px;\n}\n<\/style>\n\t<\/div>\n\t\n\n<div class=\"message-box relative dark\" style=\"padding-top:37px;padding-bottom:37px;\"><div class=\"message-box-bg-image bg-fill fill\" ><\/div><div class=\"message-box-bg-overlay bg-fill fill\" style=\"background-color:rgb(18, 18, 18);\"><\/div><div class=\"container relative\"><div class=\"inner last-reset\">\n\n\t<div id=\"gap-1593969137\" class=\"gap-element clearfix\" style=\"display:block; height:auto;\">\n\t\t\n<style>\n#gap-1593969137 {\n  padding-top: 30px;\n}\n<\/style>\n\t<\/div>\n\t\n\n<div class=\"row row-large align-center\"  id=\"row-2011648337\">\n\n\n\t<div id=\"col-1318425558\" class=\"col medium-6 small-12 large-6\"  >\n\t\t\t\t<div class=\"col-inner\"  >\n\t\t\t\n\t\t\t\n\n\t<div id=\"text-3493026347\" class=\"text max--500\">\n\t\t\n\n<h3>Need support with planning and governance?<\/h3>\n\t\t\t<\/div>\n\t\n\n\t\t<\/div>\n\t\t\t\t\n<style>\n#col-1318425558 > .col-inner {\n  padding: 0px 0px 0px 0px;\n  margin: 0px 0px 10px 0px;\n}\n<\/style>\n\t<\/div>\n\n\t\n\n\t<div id=\"col-359631282\" class=\"col medium-5 small-12 large-5\"  >\n\t\t\t\t<div class=\"col-inner text-left\"  >\n\t\t\t\n\t\t\t\n\n\t<div id=\"text-444083759\" class=\"text\">\n\t\t\n\n<p>Speak to Secure ITAD about a decommissioning scoping call.<\/p>\n\t\t\n<style>\n#text-444083759 {\n  text-align: left;\n}\n<\/style>\n\t<\/div>\n\t\n\t<div id=\"gap-1824422496\" class=\"gap-element clearfix\" style=\"display:block; height:auto;\">\n\t\t\n<style>\n#gap-1824422496 {\n  padding-top: 30px;\n}\n<\/style>\n\t<\/div>\n\t\n\n<a href=\"\/contact\/\" class=\"button primary\" style=\"border-radius:99px;\">\n\t\t<span>Get in touch<\/span>\n\t<\/a>\n\n\n\n\t\t<\/div>\n\t\t\t\t\n<style>\n#col-359631282 > .col-inner {\n  margin: 0px 0px -20px 0px;\n}\n<\/style>\n\t<\/div>\n\n\t\n\n<\/div>\n\n<\/div><\/div><\/div>\n\t<div id=\"gap-1493095156\" class=\"gap-element clearfix\" style=\"display:block; height:auto;\">\n\t\t\n<style>\n#gap-1493095156 {\n  padding-top: 30px;\n}\n<\/style>\n\t<\/div>\n\t\n\n\t<div id=\"gap-2054644908\" class=\"gap-element clearfix\" style=\"display:block; height:auto;\">\n\t\t\n<style>\n#gap-2054644908 {\n  padding-top: 30px;\n}\n<\/style>\n\t<\/div>\n\t\n\n\t<div id=\"text-2502923230\" class=\"text article-underline\">\n\t\t\n\n<h2>Phase 1: Asset discovery and reconciliation<\/h2>\n<p>If you want an audit-ready outcome, asset discovery is not optional. The baseline needs to be accurate enough that you can confidently say: \u201cEverything that should have been removed and processed has been removed and processed.\u201d<\/p>\n<p>Begin with your ITAM\/CMDB export, but don\u2019t assume it\u2019s correct. Confirm the inventory physically, capturing the information you\u2019ll need later for reconciliation and reporting: asset tag, serial number, make\/model, location (row\/rack\/unit), and whether the device is data-bearing.<\/p>\n<p>Once you have a baseline, define your reconciliation rules. In practical terms, that means deciding what counts as \u201caccounted for.\u201d For example, a device is accounted for only when it has been physically removed, recorded against the manifest, processed via the agreed data eradication method, and returned in the final reporting pack.<\/p>\n<p>This is also the point where you decide how you will handle exceptions. Devices that cannot be powered, drives that are damaged, or assets that don\u2019t match the baseline should have a documented path rather than becoming ad hoc decisions made under time pressure.<\/p>\n\t\t\t<\/div>\n\t\n\t<div id=\"gap-1030374566\" class=\"gap-element clearfix\" style=\"display:block; height:auto;\">\n\t\t\n<style>\n#gap-1030374566 {\n  padding-top: 30px;\n}\n<\/style>\n\t<\/div>\n\t\n\n\t<div id=\"text-1277742367\" class=\"text article-underline\">\n\t\t\n\n<h2>Phase 2: Decide how data will be eradicated<\/h2>\n<p>Most teams fall into a false choice: \u201cwipe everything\u201d or \u201cdestroy everything.\u201d In reality, the right approach depends on risk, policy, and the intended disposition of the equipment.<\/p>\n<p>As a simple framework:<\/p>\n<p>If the equipment will be reused or remarketed, certified erasure is usually the right starting point, because it supports value recovery while still providing evidence of sanitisation.<br \/>If the equipment carries higher sensitivity, is governed by stricter policy, or cannot be reliably wiped (for example: failed media), physical destruction is often the safer route.<\/p>\n<p>Whatever you choose, define it before execution, and ensure your reporting expectations are explicit. \u201cWe wiped it\u201d is not evidence. Evidence is a documented outcome per asset, tied back to serial numbers, with clear records of method and custody.<\/p>\n<p>If your estate includes a high proportion of SSDs, you may also want a defined physical destruction standard for those media types to avoid risk assumptions.<\/p>\n<p>CTA (box): Not sure where erasure ends and destruction begins? Speak to Secure ITAD for a data eradication recommendation aligned to your policy and risk profile.<\/p>\n\t\t\t<\/div>\n\t\n\t<div id=\"gap-406849898\" class=\"gap-element clearfix\" style=\"display:block; height:auto;\">\n\t\t\n<style>\n#gap-406849898 {\n  padding-top: 30px;\n}\n<\/style>\n\t<\/div>\n\t\n\n\t<div id=\"text-2319976467\" class=\"text article-underline\">\n\t\t\n\n<h2>Phase 3: On-site execution (de-racking, de-cabling and secure staging)<\/h2>\n<p>On-site execution is where projects either stay controlled or become chaotic.<\/p>\n<p>The safest approach is a planned sequence with a secure staging area. Your plan should specify how equipment moves from rack to staging, how it is labelled or sealed, and where custody handovers occur. If you\u2019re removing cabling, document what is removed, what remains, and how you avoid impacting adjacent live services.<\/p>\n<p>If the project is constrained by shutdown windows, plan for phased removals rather than trying to compress everything into a single high-risk day. A controlled sequence is usually faster overall because it prevents rework and reduces incidents.<\/p>\n<p>Where needed, ensure method statements and site-specific safety rules are agreed in advance, and that the vendor team is operating under the same expectations as your internal stakeholders.<\/p>\n\t\t\t<\/div>\n\t\n\t<div id=\"gap-956127694\" class=\"gap-element clearfix\" style=\"display:block; height:auto;\">\n\t\t\n<style>\n#gap-956127694 {\n  padding-top: 30px;\n}\n<\/style>\n\t<\/div>\n\t\n\n\t<div id=\"text-1493593491\" class=\"text article-underline\">\n\t\t\n\n<h2>Phase 4: Secure transport and chain of custody<\/h2>\n<p>For most organisations, the real risk isn\u2019t what happens on the rack \u2014 it\u2019s what happens between the site and the processing facility.<\/p>\n<p>Chain of custody should be treated as a series of controlled checkpoints, not a vague promise. In practical terms, that means you should be able to evidence who had custody, when custody transferred, and how assets were protected throughout the journey and any interim holding.<\/p>\n<p>Your chain-of-custody model should include clear handover points, a manifest or container ID system that ties assets to the move, and a plan for how exceptions are handled (for example: discrepancies between baseline and collected assets).<\/p>\n<p>If you can\u2019t clearly explain your custody model in a few sentences to an auditor, it\u2019s probably not robust enough.<\/p>\n\t\t\t<\/div>\n\t\n\t<div id=\"gap-1296224955\" class=\"gap-element clearfix\" style=\"display:block; height:auto;\">\n\t\t\n<style>\n#gap-1296224955 {\n  padding-top: 30px;\n}\n<\/style>\n\t<\/div>\n\t\n\n\t<div id=\"text-3765041511\" class=\"text article-underline\">\n\t\t\n\n<h2>Phase 5: Processing outcomes (remarketing, recycling and reporting)<\/h2>\n<p>Decommissioning isn\u2019t complete when equipment leaves site. It\u2019s complete when the agreed outcome has been delivered and evidenced.<\/p>\n<p>If equipment is suitable for reuse or remarketing, the processing path should protect data security first, then enable value recovery. That usually means sanitisation, testing, grading, and controlled resale routes.<\/p>\n<p>For assets that are not suitable for resale, ensure the recycling route is compliant and transparent, and that the reporting you receive supports internal and external requirements (for example, environmental reporting and WEEE-aligned processing expectations).<\/p>\n<p>What matters most is that the processing route matches what you promised stakeholders at the start: security, compliance, and commercial outcomes should not be in conflict.<\/p>\n\t\t\t<\/div>\n\t\n\t<div id=\"gap-488560101\" class=\"gap-element clearfix\" style=\"display:block; height:auto;\">\n\t\t\n<style>\n#gap-488560101 {\n  padding-top: 30px;\n}\n<\/style>\n\t<\/div>\n\t\n\n\t<div id=\"text-1492913796\" class=\"text article-underline\">\n\t\t\n\n<h2>Phase 6: Closeout pack (what \u201cdone\u201d looks like)<\/h2>\n<p>A strong closeout pack turns a stressful project into a defensible one.<\/p>\n<p>At minimum, your closeout pack should allow you to answer three questions without hesitation:<\/p>\n<p><strong>Did we account for everything?<\/strong><br \/>That\u2019s reconciliation: baseline vs collected vs processed, with exceptions explained.<\/p>\n<p><strong>Did we eradicate data appropriately?<\/strong><br \/>That\u2019s certificates or documented outcomes aligned to your agreed method, tied to serial numbers.<\/p>\n<p><strong>Did we dispose of assets responsibly?<\/strong><br \/>That\u2019s environmental and recycling reporting where applicable, plus an explanation of the final disposition paths.<\/p>\n<p>If your decommissioning partner can\u2019t supply closeout reporting that stands up to audit scrutiny, you\u2019re inheriting risk long after the project \u201cfinishes.\u201d<\/p>\n\t\t\t<\/div>\n\t\n\t<div id=\"gap-1813215865\" class=\"gap-element clearfix\" style=\"display:block; height:auto;\">\n\t\t\n<style>\n#gap-1813215865 {\n  padding-top: 30px;\n}\n<\/style>\n\t<\/div>\n\t\n\n\t<div id=\"text-2361554412\" class=\"text article-underline\">\n\t\t\n\n<h2>Vendor selection: What to ask (and how to score it)<\/h2>\n<p>Many \u201cdecommissioning checklists\u201d stop at vendor questions. Vendor due diligence is important \u2014 but it should be part of the project, not the entire project.<\/p>\n<p>When selecting a partner, focus on five areas and score them consistently:<\/p>\n<p>On-site capability and live-environment controls: can they execute safely under your access, change and shutdown constraints?<br \/>Data security and eradication options: can they support erasure, destruction, and mixed approaches with credible evidence?<br \/>Tracking and reporting: can they reconcile at serial number level and provide an audit-ready reporting pack?<br \/>Value recovery: do they have a defined remarketing process that supports commercial outcomes without compromising security?<br \/>Recycling and compliance: can they evidence compliant processing and provide reporting that meets your internal needs?<\/p>\n<p>A good scorecard prevents procurement from becoming a \u201cbest promises win\u201d exercise. It gives you comparable evidence and makes the decision defensible.<\/p>\n<p>CTA (inline): Download the Vendor Scorecard (included in the Decommissioning Toolkit).<\/p>\n\t\t\t<\/div>\n\t\n\t<div id=\"gap-1154599529\" class=\"gap-element clearfix\" style=\"display:block; height:auto;\">\n\t\t\n<style>\n#gap-1154599529 {\n  padding-top: 30px;\n}\n<\/style>\n\t<\/div>\n\t\n\n\t<div id=\"text-384530929\" class=\"text article-underline\">\n\t\t\n\n<h2>Frequently Asked Questions<\/h2>\n\t\t\t<\/div>\n\t\n<div class=\"accordion\">\n\n\t<div id=\"accordion-3462518130\" class=\"accordion-item\">\n\t\t<a id=\"accordion-3462518130-label\" class=\"accordion-title plain\" href=\"#accordion-item-can-you-decommission-in-a-live-environment?\" aria-expanded=\"false\" aria-controls=\"accordion-3462518130-content\">\n\t\t\t<button class=\"toggle\" aria-label=\"Toggle\"><i class=\"icon-angle-down\" aria-hidden=\"true\"><\/i><\/button>\n\t\t\t<span>Can you decommission in a live environment?<\/span>\n\t\t<\/a>\n\t\t<div id=\"accordion-3462518130-content\" class=\"accordion-inner\" aria-labelledby=\"accordion-3462518130-label\">\n\t\t\t\n\n\t<div id=\"text-3801404418\" class=\"text article-underline\">\n\t\t\n\n<p>Yes, but it requires tighter governance: agreed shutdown windows, controlled sequencing, clear \u201cstop work\u201d conditions, and secure staging. The goal is to reduce disruption while maintaining complete custody and reporting.<\/p>\n\t\t\t<\/div>\n\t\n\n\t\t<\/div>\n\t<\/div>\n\t\n\t<div id=\"accordion-3798182245\" class=\"accordion-item\">\n\t\t<a id=\"accordion-3798182245-label\" class=\"accordion-title plain\" href=\"#accordion-item-should-we-erase-or-destroy-our-data-bearing-devices?\" aria-expanded=\"false\" aria-controls=\"accordion-3798182245-content\">\n\t\t\t<button class=\"toggle\" aria-label=\"Toggle\"><i class=\"icon-angle-down\" aria-hidden=\"true\"><\/i><\/button>\n\t\t\t<span>Should we erase or destroy our data-bearing devices?<\/span>\n\t\t<\/a>\n\t\t<div id=\"accordion-3798182245-content\" class=\"accordion-inner\" aria-labelledby=\"accordion-3798182245-label\">\n\t\t\t\n\n\t<div id=\"text-73488203\" class=\"text article-underline\">\n\t\t\n\n<p>It depends on policy, risk profile, and intended disposition. Erasure can support reuse and value recovery; destruction is often appropriate for higher sensitivity or failed media. The key is agreeing the method upfront and documenting outcomes per asset.<\/p>\n\t\t\t<\/div>\n\t\n\n\t\t<\/div>\n\t<\/div>\n\t\n\t<div id=\"accordion-896609206\" class=\"accordion-item\">\n\t\t<a id=\"accordion-896609206-label\" class=\"accordion-title plain\" href=\"#accordion-item-what-evidence-should-we-keep-after-the-project?\" aria-expanded=\"false\" aria-controls=\"accordion-896609206-content\">\n\t\t\t<button class=\"toggle\" aria-label=\"Toggle\"><i class=\"icon-angle-down\" aria-hidden=\"true\"><\/i><\/button>\n\t\t\t<span>What evidence should we keep after the project?<\/span>\n\t\t<\/a>\n\t\t<div id=\"accordion-896609206-content\" class=\"accordion-inner\" aria-labelledby=\"accordion-896609206-label\">\n\t\t\t\n\n\t<div id=\"text-4097071579\" class=\"text article-underline\">\n\t\t\n\n<p>Keep reconciliation records, certificates or documented sanitisation\/destruction outcomes tied to serial numbers, and disposal\/recycling reporting where applicable. If an auditor asked for proof months later, you should be able to provide it quickly.<\/p>\n\t\t\t<\/div>\n\t\n\n\t\t<\/div>\n\t<\/div>\n\t\n\t<div id=\"accordion-693152392\" class=\"accordion-item\">\n\t\t<a id=\"accordion-693152392-label\" class=\"accordion-title plain\" href=\"#accordion-item-how-do-you-prevent-asset-loss?\" aria-expanded=\"false\" aria-controls=\"accordion-693152392-content\">\n\t\t\t<button class=\"toggle\" aria-label=\"Toggle\"><i class=\"icon-angle-down\" aria-hidden=\"true\"><\/i><\/button>\n\t\t\t<span>How do you prevent asset loss?<\/span>\n\t\t<\/a>\n\t\t<div id=\"accordion-693152392-content\" class=\"accordion-inner\" aria-labelledby=\"accordion-693152392-label\">\n\t\t\t\n\n\t<div id=\"text-4253301016\" class=\"text article-underline\">\n\t\t\n\n<p>Asset loss risk is reduced through accurate baseline discovery, controlled labelling and manifests, defined custody checkpoints, and reconciliation rules that only mark assets \u201cclosed\u201d once processing evidence is received.<\/p>\n\t\t\t<\/div>\n\t\n\n\t\t<\/div>\n\t<\/div>\n\t\n\t<div id=\"accordion-4137451703\" class=\"accordion-item\">\n\t\t<a id=\"accordion-4137451703-label\" class=\"accordion-title plain\" href=\"#accordion-item-can-you-help-with-multi-site-programmes?\" aria-expanded=\"false\" aria-controls=\"accordion-4137451703-content\">\n\t\t\t<button class=\"toggle\" aria-label=\"Toggle\"><i class=\"icon-angle-down\" aria-hidden=\"true\"><\/i><\/button>\n\t\t\t<span>Can you help with multi-site programmes?<\/span>\n\t\t<\/a>\n\t\t<div id=\"accordion-4137451703-content\" class=\"accordion-inner\" aria-labelledby=\"accordion-4137451703-label\">\n\t\t\t\n\n\t<div id=\"text-1079340733\" class=\"text article-underline\">\n\t\t\n\n<p>Yes. Multi-site decommissioning benefits from standardised templates, consistent custody rules, and a repeatable closeout pack format so reporting stays uniform across locations.<\/p>\n\t\t\t<\/div>\n\t\n\n\t\t<\/div>\n\t<\/div>\n\t\n\n<\/div>\n\n","protected":false},"excerpt":{"rendered":"","protected":false},"author":1,"featured_media":3991,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[77,76],"tags":[],"class_list":["post-12769","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-gidsen","category-guides"],"_links":{"self":[{"href":"https:\/\/www.secure-itad.com\/nl\/wp-json\/wp\/v2\/posts\/12769","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.secure-itad.com\/nl\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.secure-itad.com\/nl\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.secure-itad.com\/nl\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.secure-itad.com\/nl\/wp-json\/wp\/v2\/comments?post=12769"}],"version-history":[{"count":1,"href":"https:\/\/www.secure-itad.com\/nl\/wp-json\/wp\/v2\/posts\/12769\/revisions"}],"predecessor-version":[{"id":12774,"href":"https:\/\/www.secure-itad.com\/nl\/wp-json\/wp\/v2\/posts\/12769\/revisions\/12774"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.secure-itad.com\/nl\/wp-json\/wp\/v2\/media\/3991"}],"wp:attachment":[{"href":"https:\/\/www.secure-itad.com\/nl\/wp-json\/wp\/v2\/media?parent=12769"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.secure-itad.com\/nl\/wp-json\/wp\/v2\/categories?post=12769"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.secure-itad.com\/nl\/wp-json\/wp\/v2\/tags?post=12769"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}