iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
Preserve evidence before routine cleanup changes it. Activate your incident-response plan, document the scene, prioritize volatile data and short-retention logs, make containment decisions with a qualified responder, and protect original media while creating verified forensic copies. The right order depends on the threat, system, safety consequences, available expertise, and legal constraints.
What to do in the first hour
A suspected ransomware attack, unauthorized access, or insider incident can alter evidence every minute. Start an incident log and assign an incident lead, a technical collection lead, a person authorized to approve containment, a legal contact, and a business owner for each affected service. Use your organization’s evidence-handling procedure if one exists.
- Notify the response team. Contact security or IT operations, management, legal counsel, and the owner of the affected business service. Identify who may authorize collection, who is trained to collect it, and who communicates with cloud or managed-service providers.
- Freeze routine changes. Tell staff not to reimage, reboot, delete files, run cleanup tools, install troubleshooting software, or continue browsing on a suspected device unless the incident lead and technical responder approve the action.
- Record the current state. Note what was observed, by whom, when, on which device or account, and what has already happened. Capture original alerts and relevant screens or exports without exploring unrelated files.
- Assess immediate harm. Determine whether the system is still communicating, encrypting data, endangering people, or affecting critical operations. A safety or life-preservation decision takes priority, but document what was done and why.
- Ask a trained responder to prioritize volatile evidence. Memory, running processes, active connections, and short-retention logs may disappear when state changes.
This sequence reflects principles in NIST SP 800-86, Guide to Integrating Forensic Techniques into Incident Response (2006), NIST SP 800-61 Rev. 2 (2012), and CISA ransomware guidance. Those documents are useful technical references, but your current organizational procedure and counsel’s direction control the response.
The Tool Desk
Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Set roles and authority before collection
Evidence handling fails when everyone assumes someone else is responsible. Write down the authority and handoffs before a responder starts collecting data.
#1 Best Overall
- Read Before You Buy — No Video Output: These adapters support charging and USB 2.0 data transfer, but cannot transmit video signals. Except for standard USB webcams (which use USB data only), they are not compatible with HDMI/DisplayPort cables, video-capable USB-C hubs, or docking stations with video output.
- Convert USB-A Ports to USB-C: Designed to connect USB-C earphones, cables, flash drives, card readers, and other USB-C accessories to standard USB-A ports. Plug-and-play with no drivers or software required.
- Aluminum Alloy Housing: Built with a sturdy aluminum alloy shell that aids in heat dissipation and protects against daily wear and scratches. Designed to maintain a stable and secure connection.
- Compact & Travel-Friendly: The ultra-compact design allows the adapter to stay plugged into your device without blocking adjacent ports or adding bulk, reducing wear and tear on your original USB ports.
- 12-Month Warranty: Backed by a 12-month manufacturer warranty for peace of mind. Designed to meet strict quality control standards for reliable everyday performance.
Incident lead
The incident lead coordinates containment, preservation, recovery, communications, and business priorities. This person maintains the master timeline and records decisions that could affect evidence.
Technical collection lead
The collection lead chooses appropriate live-response, imaging, export, and verification methods. Collection should be performed by personnel who understand the operating system, storage technology, cloud service, and the changes their tools can make.
Legal and privacy contact
Counsel should determine whether employee devices, personal accounts, customer records, communications, or third-party data may be searched or copied. Counsel also coordinates litigation holds, contractual duties, and any required notifications. This article is not jurisdiction-specific legal advice.
Service and business owners
Owners of identity systems, email, endpoint tools, firewalls, VPNs, backups, and cloud tenants can identify where records live and how long they are retained. They should not independently alter settings or purge data while preservation decisions are pending.
Document the scene before changing it
Create a timestamped incident log as soon as the event is recognized. Use a consistent time zone, preferably recording the local time zone and UTC where your procedure permits. Keep the log in controlled storage and preserve its original entries.
Record device and account identifiers
- Hostname, asset tag, serial number, model, and operating-system version
- Assigned user, relevant account names, tenant or subscription identifiers, and administrator identities
- IP and network identifiers, physical location, and logical segment when relevant
- Cloud service, region or tenant, date range, and affected resources
- Where the item was found and who had control of it
Record observations and prior actions
Write what the observer actually saw: ransom notes, unusual prompts, alerts, changed files, login warnings, unavailable systems, or suspicious messages. Include the observer’s name and the observation time. Record reboots, network changes, account disables, password resets, tool executions, or other actions that happened before the response began. If a fact is uncertain, label it as uncertain rather than filling the gap with an assumption.
Rank #2
- 5-in-1 USB-C Hub: Experience comprehensive connectivity featuring a Power Delivery input, two USB-A 2.0 ports, a USB-A 3.0 port, and an HDMI port. (Note: The USB-C power delivery input port is only for connecting an external wall charger to power your laptop and cannot power peripheral devices.)
- 90W Pass-Through Charging: Achieve optimal charging with 90W pass-through power to your laptop, supported by a total input of 100W, with the hub reserving 10W for operational efficiency. (Note: Wall charger not included.)
- Quick Data Transfers: Accelerate your productivity with rapid data transfers using a high-speed 5Gbps USB 3.0 port and two 480Mbps USB 2.0 ports.
- 4K HDMI Display: Enhance your visual experience with a hub capable of delivering 4K resolution at 30Hz in both mirror and extend modes. Please note that this hub is compatible with MacBook (macOS 12 and newer), Windows 10 and 11, ChromeOS, and laptops equipped with DP Alt Mode and Power Delivery. Note: This device is not compatible with Linux.
- What You Get: Anker USB-C Hub (5-in-1, 4K HDMI), welcome guide, 18-month warranty, and our friendly customer service.
Preserve original alerts and exports
Export relevant alerts, email headers, endpoint detections, firewall events, and screenshots according to the product’s approved method. Keep the original export and record the tool, account, time, filters, and date range used. Do not casually open files on a suspect endpoint, run a search across the user’s profile, or ask the user to continue working on it; interaction can alter timestamps, memory, logs, and file metadata.
Do these 3 things before closing this tab:
1Fix the driver behind crashes, sound loss and screen glitches2Clear out junk files and repair common Windows errors3Scan for outdated or missing drivers - takes under a minutePrioritize volatile data and short-retention records
Digital evidence has different lifetimes. NIST recommends prioritizing sources by likely evidentiary value, volatility, and collection effort. CISA specifically identifies memory and limited-retention logs as information that may need prompt preservation.
Potentially volatile endpoint data
A qualified responder should decide whether to capture live data before isolating or shutting down a host. Depending on the operating system and incident, useful sources may include:
- Physical memory
- Running processes and loaded modules
- Logged-on users and active sessions
- Open files and listening or established network connections
- Recent command or script activity
- Operating-system, firewall, and security-tool buffers
- Encryption state, mounted volumes, and removable media status
Live collection can itself change system state. Record the collection tool and version, commands or modules used, start and end times, destination media, errors, and what could not be collected. Never imply that a live capture is complete merely because it finished without an error.
Identify retention windows in parallel
Ask service owners how long records remain available and whether retention can be extended without altering the underlying event history. Check identity and access systems, email, endpoint detection, VPN, firewall, DNS, proxy, network-device, backup, and cloud audit records. Export the relevant date range under the approved procedure and record the query, filters, account, export format, and timestamps.
Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minuteWindows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallA record that expires tomorrow may be more urgent than a disk image that can be acquired later. Conversely, a high-risk host may require containment first. The incident lead and trained responder should document that trade-off.
Rank #3
- Sleek 7-in-1 USB-C Hub: Features an HDMI port, two USB-A 3.0 ports, and a USB-C data port, each providing 5Gbps transfer speeds. It also includes a USB-C PD input port for charging up to 100W and dual SD and TF card slots, all in a compact design.
- Flawless 4K@60Hz Video with HDMI: Delivers exceptional clarity and smoothness with its 4K@60Hz HDMI port, making it ideal for high-definition presentations and entertainment. (Note: Only the HDMI port supports video projection; the USB-C port is for data transfer only.)
- Double Up on Efficiency: The two USB-A 3.0 ports and a USB-C port support a fast 5Gbps data rate, significantly boosting your transfer speeds and improving productivity.
- Fast and Reliable 85W Charging: Offers high-capacity, speedy charging for laptops up to 85W, so you spend less time tethered to an outlet and more time being productive.
- What You Get: Anker USB-C Hub (7-in-1), welcome guide, 18-month warranty, and our friendly customer service.
Choose containment without destroying evidence
There is no universal rule to pull the plug, disconnect every cable, or leave a compromised computer connected. Isolation can stop lateral movement or ongoing damage; powering down can remove memory and other volatile information; leaving a host online can allow further compromise. The choice depends on the threat, system, safety risk, business impact, and collection capability.
| Question | If the answer is “high” | What to document |
|---|---|---|
| Is the host actively harming other systems or people? | Containment may require urgent network isolation or shutdown. | Observed harm, approving authority, exact action time, and safety or operational rationale. |
| Could memory or active connections reveal the attack? | Attempt qualified live collection before a state-changing action, when safe. | What was captured, by whom, with which tool and time. |
| Is a trained responder and suitable tooling available? | Escalate to internal or external incident-response expertise before collection. | Who was contacted, when, and the advice received. |
| Would isolation interrupt a critical service? | Use the business continuity and safety process while preserving adjacent logs and records. | Expected outage, alternatives considered, and authorization. |
| Could a legal or privacy restriction apply? | Pause searches of personal, employee, or third-party data until counsel sets scope. | Scope decision, data categories, and counsel’s instructions. |
Record each containment action separately: network-port change, account disablement, host isolation, service stop, shutdown, or power removal. Include the exact time zone, operator, affected identifier, and reason. Do not describe one sequence as correct for every ransomware or intrusion case.
Acquire forensic copies while protecting originals
Use an acquisition plan appropriate to the device, storage medium, operating system, and incident. If storage imaging is appropriate, preserve the original and perform analysis on a working copy whenever practicable.
Quick wins for a faster PC:
Repair Windows errors before they cause bigger problemsFix Now →Scan for outdated or missing drivers - takes under a minuteDriver Scan →Clear out junk files and repair common Windows errorsFree Scan →Use a write blocker for storage imaging
NIST defines a write-blocker as a hardware- or software-based tool that prevents a computer from writing to connected storage media. A suitable write blocker reduces the chance that the acquisition computer changes the original media. Confirm interface compatibility and test the approved workflow before an incident; purchasing a blocker does not replace training or a documented procedure.
Record acquisition details
- Source device identifier, media serial number, capacity, and condition
- Destination identifier and whether the destination is approved, write-protectable, or write-once media
- Acquisition tool name and version, operator, workstation, and configuration
- Start and end times with time zone
- Read errors, bad sectors, skipped areas, interruptions, and retries
- Image format, size, and verification results
Verify copied-data integrity
Calculate message digests or hashes for the acquired image and, where your procedure requires it, for the source or subsequent copies. Compare the results and preserve the verification record with the evidence. A matching digest supports detection of later alteration; it does not prove that collection was complete, lawful, or technically correct.
Seal and secure original media with controlled access. Restrict write access to forensic images and keep analysis derivatives separate from the evidentiary original. If an examiner must work from a copy, label it as a working copy and record how it was created.
Rank #4
- Dual Converters, Infinite Potential：Includes 2× USB C male to USB A female adapters and 2× USB A male to USB C female adapters. Perfect for a wide range of uses—tablets with Bluetooth keyboards, expand USB ports on macbook, and more. Two different converters for all your daily needs
- Next-Level 10Gbps & 3A Charging: No more slow 480Mbps, this usb to usb c adapter has a transfer speed of up to 10Gbps, allowing you to do more transferring in less time. This usb adapter fits both USB A and USB C charger, supporting up to 3A fast charging
- Upgraded Exquisite Craftsmanship: With an aluminum alloy housing and metal connector, the usbc to usb adapter is extremely durable and sturdy. Rigorously tested to withstand more than 10,000 times of plugging and unplugging, ensuring long-lasting performance
- Broad Compatible: The usb c to usb adapter widely supports all USB C/ USB A devices like laptops, tablets, cellphones, car chargers, and phone chargers. Such as compatible with MacBook Pro/Air 2023/2022, Thunderbolt 4/3 Devices,Apple MagSafe Watch 9/8/7/SE/Ultra, iPad Pro 2022/2021, Samsung Galaxy S23/S20/S10, and iPhone 17/16/15 Pro. Plug and play
- Please Note: To reach 10Gbps speed, keep the cable under 3.3 ft. For USB A Male to USB C adapters, try flipping the USB C connector. USB C Male to USB A adapters support bidirectional 10Gbps transfer within 3.3 ft
Preserve cloud, identity, and provider evidence
Cloud evidence is distributed across tenants, services, accounts, regions, and provider-controlled systems. NIST SP 800-201, Cloud Computing Forensic Reference Architecture (2024), emphasizes readiness and planning rather than one universal collection procedure.
Define the cloud scope
Identify the tenant or subscription, affected accounts, administrative roles, services, resources, date range, and time zone. List identity events, authentication records, administrative changes, object access, configuration changes, and relevant workload or platform logs. Note whether a managed-service operator, reseller, or separate security provider controls any records.
Ask about retention and export constraints
Promptly ask the provider or service operator how to preserve records, extend retention, place a hold, or export data without changing its state. Record the request, recipient, response, export method, filters, timestamps, and any fields that were unavailable. A provider’s export may have its own format, clock, pagination, or completeness limitations; keep the provider’s documentation with the export.
Preserve identity and administrative history
Prioritize sign-ins, multifactor-authentication events, token or key changes, privilege assignments, mailbox rules, forwarding changes, API activity, and administrator actions when they fall within the incident window. Preserve the configuration context needed to interpret those events, including account status, role assignments, and relevant policy changes.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Maintain chain of custody and secure storage
A custody record shows who controlled an item and what happened to it. Label every device, image, export, and working copy with a unique identifier tied to the incident.
| Custody entry | Information to capture |
|---|---|
| Initial collection | Item identifier, description, source, collector, date and time with time zone, and collection location. |
| Transfer | Transferor, recipient, date and time, purpose, signatures or approved electronic attestations, and package or seal condition. |
| Storage | Controlled storage location, access restrictions, environmental or handling requirements where relevant, and check-in time. |
| Copy or derivative | Parent item, tool and version, operator, creation time, digest or verification result, and working-copy designation. |
| Return or disposition | Authorization, recipient or destruction method, date, and final status under the organization’s procedure. |
NIST SP 800-61 Rev. 2 specifically calls for identifiers, handlers, dates and times including time zone, and storage locations in the evidence log. Keep evidence separate from routine administrative files, limit access to authorized personnel, and monitor for alteration or loss.
Best Value
- 5-in-1 Connectivity: Equipped with a 4K HDMI port, a 5 Gbps USB-C data port, two 5 Gbps USB-A ports, and a USB C 100W PD-IN port. Note: The USB C 100W PD-IN port supports only charging and does not support data transfer devices such as headphones or speakers.
- Powerful Pass-Through Charging: Supports up to 85W pass-through charging so you can power up your laptop while you use the hub. Note: Pass-through charging requires a charger (not included). Note: To achieve full power for iPad, we recommend using a 45W wall charger.
- Transfer Files in Seconds: Move files to and from your laptop at speeds of up to 5 Gbps via the USB-C and USB-A data ports. Note: The USB C 5Gbps Data port does not support video output.
- HD Display: Connect to the HDMI port to stream or mirror content to an external monitor in resolutions of up to 4K@30Hz. Note: The USB-C ports do not support video output.
- What You Get: Anker 332 USB-C Hub (5-in-1), welcome guide, our worry-free 18-month warranty, and friendly customer service.
Handle employee, customer, and third-party data lawfully
Workplace evidence may contain personal messages, health information, customer records, credentials, source code, or data belonging to another organization. Before searching an employee device, personal account, communications archive, or shared service, counsel should determine the lawful scope and applicable employment, privacy, data-protection, contractual, and evidence requirements.
Set a collection scope
Define the systems, accounts, date range, file types, and incident questions that justify collection. Use the least intrusive approved method that answers the question. Do not broaden a search simply because additional data is easy to copy.
Coordinate holds and notifications
If counsel directs a litigation hold or incident hold, preserve the identified information and document the hold’s scope. Have counsel and the incident lead assess regulatory or contractual notification duties and deadlines for the relevant jurisdiction and facts. No single deadline applies to every organization or incident.
Protect sensitive copies
Encrypt or otherwise secure evidence in transit and at rest according to organizational policy. Keep access logs and disclose evidence only to people whose role requires it. A chain-of-custody form supports traceability; it does not by itself establish that a collection was lawful or that the data is admissible in court.
Common mistakes that destroy useful evidence
- Reimaging before collection: Reinstallation removes or overwrites files, logs, and artifacts that may explain the intrusion.
- Immediate power removal as a reflex: Power loss can erase memory and active connections. It may still be necessary to stop severe harm, but record the decision and seek responder advice first when safe.
- Leaving a host connected without assessment: An attacker may continue moving laterally, encrypting files, or deleting logs.
- Running cleanup or optimization software: Automated changes can modify timestamps, remove files, or overwrite free space.
- Working on the only original: Analysis can alter metadata and state. Create a verified working copy.
- Collecting without a time zone: Events from different systems become difficult to correlate.
- Ignoring cloud retention: Provider logs may expire while a team focuses only on local disks.
- Assuming a hash proves everything: A digest detects changes to the hashed data; it does not prove that the right source was selected or that collection was complete.
- Searching personal data without counsel: Scope and privacy errors can create a second incident and compromise the investigation.
A practical preservation checklist
Use this checklist as a prompt, then follow your organization’s approved procedure.
- Open a timestamped incident log and select one time zone.
- Assign incident, technical, legal, business-owner, and communications roles.
- Record host, account, tenant, network, physical-location, and observer details.
- Preserve original alerts, screenshots, headers, and approved exports.
- Ask a qualified responder to assess memory, processes, connections, and other volatile data.
- List every affected log source and its retention window.
- Decide on isolation, shutdown, or continued operation using threat, safety, business, and volatility factors.
- Record the rationale and exact time for each containment action.
- Acquire appropriate forensic copies with approved tools and a write blocker where applicable.
- Calculate and record message digests or other integrity checks.
- Secure originals, images, exports, and working copies with controlled access.
- Open a custody entry for every collection, transfer, copy, and storage change.
- Identify cloud providers, managed services, accounts, date ranges, and export limits.
- Ask counsel to define privacy, employment, contractual, hold, and notification requirements.
- Brief the recovery team on what must not be altered until the incident lead releases it.
What happens after preservation
Once the agreed evidence is secured, the incident lead can authorize examination, eradication, and recovery in separate documented stages. Analysts should work from verified copies, preserve examination notes, and link findings to the item identifiers and time line. Recovery changes should be recorded so later reviewers can distinguish original evidence from remediation artifacts.
NISTIR 8387 (2022), Digital Investigation Techniques: A NIST Scientific Foundation Review, and the earlier NIST publications provide useful background for documenting methods and limitations. Because NIST SP 800-86 and SP 800-61 Rev. 2 are older guides, confirm current editions, organizational procedures, and provider capabilities before relying on a specific workflow. No preservation practice guarantees courtroom admissibility; that conclusion depends on the law, facts, collection quality, and complete process documentation.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
