/ Guide / The return leg
Device lifecycle management is judged on the return leg.
Deployment gets the attention, but IT asset lifecycle management is where multi-site operations lose control: units leave a site and nobody can say later where they went, whether the drive was erased, or what the site is still owed.
Surya operates that leg as part of Surya Endpoint, with each device and each handoff recorded by serial number. The devices remain yours throughout.
/ Coming back
Return, repair, warranty movement.
Failed, retired and departed devices come back through a documented path. Surya manages returns, repair, warranty movement, certified erasure and retirement, and routes each unit according to what it is: a repairable device goes for repair or warranty handling and returns to inventory once it meets the standard again; a device that no longer meets the released specification does not go back into service.
Existing equipment is reused only where hardware, firmware, support life, security capability and recovery tests meet the released specification. That test applies on the way back in, not only at first purchase.
/ Retirement
Certified retirement, per serial number.
Where erasure applies, drives are erased to NIST 800-88 with a certificate filed against the serial number, before approved disposition. The unit is then closed against its record. That certificate is the artifact your auditors ask for, and it exists per device rather than as a summary statement about a batch.
Retirement is treated as an operating step rather than a clearance exercise at the end of a year. A device leaves service when it stops meeting the released specification or when the person it was issued to leaves, and in both cases the same path applies: return under custody, erasure where erasure applies, approved disposition, record closed. Departed-employee devices follow that path too, which is what keeps the count of machines in service equal to the count the standard says should exist.
/ Refresh
Refresh through the on-site replacement.
Refresh does not need a separate program. Where a released Endpoint profile includes physical recovery, the prepared replacement at the site is already on the current approved build, so a device reaching end of support is retired through the same controlled swap the operation already knows. Replenishment, refresh and retirement keep every location on the supported setup.
An emergency is not a moment for an unplanned migration. Replacement fits where the Surya configuration and its dependencies are already qualified, which is why the standard is agreed before the first site goes in.
/ Records
Records you can audit.
- Every device and every handoff recorded by serial number.
- Swaps authorized and recorded, so an issuance has an owner.
- Requests, troubleshooting and changes inside the supported environment producing an operational record available for review.
- Erasure certificates filed per device where erasure applies.
- Controlled and logged access to Surya facilities.
Because the assets and licensing are yours, leaving is a transition rather than a rebuild. Exit treatment comes from the approved agreement.
Check Fit.
Tell us how many devices are in service across your sites and what you need to be able to prove.
Check Fit