058 - TechServ Foundation - Pending getting more members -

Project Proposal: TechServ Foundation
1. Executive Summary
• Objective: To significantly increase computer hardware donations to TechServ by eliminating donor concerns regarding data privacy and providing an enterprise-grade audit trail.
• Solution: A dual-component software ecosystem consisting of a donor-facing Web Portal and a bootable, network-isolated Wiping Operating System. The system allows donors to pre-register assets, specify data destruction standards, and receive verifiable cryptographic certificates of destruction.
• Impact: Builds trust with institutional and individual donors, streamlines TechServ’s internal refurbishment and intake workflows, and guarantees compliance with modern data privacy standards, furthering TechServ's mission to bridge the digital divide.
2. System Architecture
The project is divided into two core components that communicate via a secure, local-to-cloud bridge to prevent malware cross-contamination from donated hardware.
Component A: SecureDonor Web Portal (Public & Admin)
• Donor Portal: Secure login for donors to pre-register assets via bulk CSV upload or manual entry. Generates printable QR/barcode labels for physical drop-off.
• Wipe Standard Selection: Dropdown for donors to select their required wiping standard (e.g., NIST 800-88 Purge, NIST 800-88 Clear) for pre-registered drives.
• Certificate Vault: A secure dashboard where donors can view, download (PDF), and verify digital certificates of destruction.
• TechServ Admin Interface: A management dashboard for volunteers to track pending donations, view wipe error logs, and transition wiped hardware into the "Ready to Refurbish" inventory state.
Component B: TechServ "SanitizeOS" (Bootable Utility)
• Bootable Linux Environment: A lightweight, custom Linux ISO flashed to USB drives. Volunteers boot donated machines directly into this OS, bypassing the existing (and potentially infected) host operating system.
• Isolated Network Intake: The bootable OS connects to an isolated, air-gapped TechServ VLAN to query the local database for pre-registered serial numbers and wipe instructions.
• Smart Hardware Detection & Wiping:
◦ Automatically identifies drive medium.
◦ HDDs: Executes the donor-selected multi-pass or single-pass cryptographic overwrite.
◦ SSDs/NVMe: Bypasses standard overwrites to prevent drive degradation, instead issuing hardware-level ATA Secure Erase or NVMe Format commands to flush memory cells instantaneously.
• Automated Verification: Performs a post-wipe verification read to confirm no data remains.
• Certificate Generation: Generates a cryptographic receipt (Serial Number, Timestamp, Standard, Hash) and pushes it to the local server, which syncs with the Web Portal.
3. Core Workflows
Phase 1: Pre-Registration & Tagging
1. Donor logs into the Web Portal and uploads serial numbers for 20 laptops.
2. Donor selects "NIST 800-88 Purge" for the batch.
3. Portal generates a PDF of QR codes. The donor prints these, tapes them to the laptops, and drops them off at the TechServ office.
Phase 2: Intake & Execution
1. A TechServ volunteer receives the laptops. They scan the QR code using a USB barcode scanner, marking the asset as "Received" in the Admin Interface.
2. The volunteer inserts the SanitizeOS USB into the laptop and boots the system.
3. SanitizeOS automatically reads the drive's serial number, pulls the requested NIST standard from the local server, and initiates the correct wipe (issuing an ATA Secure Erase if an SSD is detected).
Phase 3: Verification & Reporting
1. The wipe finishes and is verified by the software.
2. SanitizeOS pushes the completion data to the server.
3. The Web Portal generates the digital certificate and sends an automated email to the donor: "Assets sanitized. View your certificates."
4. The volunteer unplugs the USB, and the laptop is categorized as "Ready for OS Install" in the TechServ inventory.
4. Exception Handling: The Physical Destruction Protocol
If a drive is failing, contains bad sectors, or has a dead controller, the software wipe will inevitably fail or hang.
• Software Trigger: If SanitizeOS detects a wipe failure, it flags the serial number with a red "Requires Physical Destruction" error on the volunteer's screen and the Admin Portal.
• Manual Intervention: The volunteer removes the physical drive from the machine and physically destroys it (e.g., via drill press or shattering).
• Certificate Override: The volunteer logs into the Admin Portal, locates the flagged serial number, and manually attests to physical destruction. The system generates a "Certificate of Physical Destruction" for the donor in place of a digital wipe certificate.