Connect containment, evidence, identity, vendors, backups, and recovery under one incident owner. Call to confirm availability, authority, access, and the response engagement.
500+ customers served. Backed by 100+ professionals and technical resources across our delivery network.
CONTAIN. RECOVER. VALIDATE. HARDEN.
One coordinated incident response.
Connect identity, endpoint, backup, cloud, and vendor evidence. Preserve the record, control the next actions, and validate the business workflow before calling it recovered.
REMOTE TRIAGE: CALL TO CONFIRM AVAILABILITYONSITE: TIMING CONFIRMED FOR YOUR LOCATIONNON-RETAINED RESPONSE: FROM $500/HRRETAINED RESPONSE: FROM $400/HR
Two-hour minimum. Urgency, after-hours work, travel, tooling, hardware, and third-party costs are confirmed before work begins.
The wrong first move can erase evidence, spread the attack, or turn a clean restore into another infected system. Call to confirm response availability and coordinate next steps with the incident owner. Preserve evidence and avoid uncoordinated changes.
Do not make it worse
Do not start cleaning before someone owns the timeline.
Do not wipe, rebuild, or reimage affected systems.
Do not delete ransom notes, suspicious files, alerts, logs, or quarantined items.
Do not restore over infected systems until a clean point and recovery order are confirmed.
Do not let every vendor make live changes without one incident owner.
Do not contact or pay attackers without counsel, insurer, and leadership direction.
Before remote triage starts
Have the facts and authority ready.
A decision-maker who can approve emergency work.
A clean phone bridge or screen share with someone who knows the environment.
Remote access that still works, or someone onsite who can drive under direction.
Admin contacts for identity, M365, EDR, firewall/VPN, backup, hypervisor, cloud, and key apps.
The business priority: what must be restored first and what can wait.
Freeze-the-scene checklist
Preserve the story before the story changes.
TimeWrite down when the first symptom appeared and who found it.
EvidencePhotograph ransom notes, error screens, hostnames, filenames, and alerts.
SystemsIsolate affected hosts if spread is active. Do not wipe or reboot them blindly.
LogsPreserve EDR alerts, firewall/VPN logs, M365 sign-ins, and backup job history.
BackupsProtect backup consoles and admin accounts. Do not prune old restore points.
ChangesList every fix, reboot, password reset, vendor action, and restore attempt already made.
Pricing starts with triage because every incident is different. We quote urgency, after-hours work, travel, tooling, hardware, and third-party costs before work starts.
Remote Critical Recovery
Non-retained from $500/hr
For active ransomware, suspicious infection, failed restores, dead systems, and urgent vendor loops that require coordinated remote recovery. Call to confirm availability and scope.
Call to confirm remote triage availability
Containment, evidence, and recovery plan
Retained clients from $400/hr
Critical Onsite Response
Onsite availability confirmed for your location.
For environments where someone needs to be physically present: damaged access, offline infrastructure, hands-on recovery, or executive pressure.
Onsite timing and travel confirmed before engagement
International onsite timing confirmed around flights, access, and safety
Travel, lodging, hardware, and tools billed separately
Ransomware War Room
One owner across every console
For teams that already have tools but need someone to connect signals, direct vendors, validate restores, and brief leadership.
Identity, endpoint, firewall, cloud, and backup coordination
Initial action list and recovery order
Leadership incident brief after stabilization
Two-hour minimum on emergency response. Active security incidents, after-hours, weekend, high-risk, and travel work may carry a higher quoted rate. U.S. and international onsite availability and timing are confirmed around location, flights, access, and safety.
Initial response
Make the chaos smaller.
Ransomware gets expensive when every tool, vendor, and department is shouting from a different corner. 3PS creates the response lane, controls the next actions, and keeps leadership out of guesswork.
Review risky sign-ins, disable suspect accounts, revoke sessions, tighten conditional access, and confirm which admins still need control.
02
Contain hosts
Isolate infected endpoints and servers, preserve volatile evidence, stop known indicators, and keep clean systems clean.
03
Protect backups
Confirm backup integrity, check immutability and retention, identify known-good restore points, and avoid restoring compromised data.
04
Control vendors
Pull firewall, EDR, M365, backup, cloud, and network vendors into one fact pattern so the incident stops bouncing between queues.
05
Plan recovery
Prioritize the workflows that make money, move patients, ship orders, or keep leadership accountable. Restore the business, not just devices.
06
Brief leadership
Write what is known, unknown, contained, exposed, restored, and still at risk in plain English.
Where it usually breaks
The stack had pieces. Nobody owned the pressure.
CrowdStrike, SentinelOne, Bitdefender, Darktrace, M365 Defender, SIEM, firewalls, backups, and mail tools can all help. They still do not replace incident ownership.
Endpoint-only response
The endpoint alert was real, but the stolen session was already moving.
3PS correlates endpoint activity with M365 sign-ins, mailbox rules, identity risk, cloud access, and remote access logs.
Backup confidence
The backup dashboard was green. The restore path was not validated.
3PS validates clean restore points, rebuild order, dependencies, and what the business can safely bring online first.
Vendor loop
Every vendor says their console is green while the business is still down.
3PS forces a single timeline, tests each claim, and turns vague support answers into accountable next steps.
No incident brief
Leadership gets noise instead of a record they can act on.
3PS produces a clear incident record: what failed, where it failed, what changed, what remains, and what prevents round two.
Incident brief
Recovery is not done until the story is explainable.
Executives, insurers, counsel, customers, and vendors need the same thing: a defensible record. Not screenshots thrown into a folder. A timeline, decisions, evidence, and remaining risk.
TimelineWhen it started, how it moved, and when it was contained.
ScopeUsers, hosts, servers, cloud apps, backups, and third parties touched.
Root causeLikely entry point, contributing gaps, and what still needs confirmation.
Next controlsMonthly monitoring, restore testing, stack management, and runbooks.
ILLUSTRATIVE PLANNING MODEL
Understand the exposure.
Five days down at an assumed $10,000 per hour is $1.2 million before incident response. Replace the defaults with your own operating impact, downtime window, and environment size.
The comparison uses current service starting investments with an annual commitment. It is not a quote, a loss forecast, or a prediction of avoided downtime.
$60,000 at $500/hr (120 modeled response hours; two-hour minimum)
Total modeled exposure
$1,260,000
Exposure / annual estimate
18.3x annual estimate
Annual estimate / hourly business loss
6.9 hours of assumed business loss
Monthly service starting investment
Readiness: from $5,000/mo, annual commitment; resources scoped in the proposal.
Illustrative security tools
$745/mo, $8,940/yr illustrative software estimate
User count used
25 users
The endpoint/email bundle uses 25 units: the greater of 25 users and 25 endpoints, with a 25-user minimum. Plus 3 servers, 8 switches/APs, and 1 firewall.
The equivalent-hours figure is arithmetic only. It does not show how much downtime an engagement will prevent or imply that the investment pays for itself.
Planning estimate: from $5,745/mo, with an annual commitment from $68,940/year. The engagement, engineering resources, working hours, and response commitments are scoped in the proposal. Software is a separate illustrative estimate based on the device mix. These figures are not a quote or a guarantee of prevention or savings.
Readiness and operations engagements are annual commitments billed monthly. Covered systems, engineering resources, working hours, review cadence, and response commitments are defined in the proposal. Software and security tools are included only when stated in the agreement.
Monthly ownership
We learn the environment before the clock is burning money.
Recurring reviews of identity, endpoints, servers, backups, network devices, cloud apps, vendor risks, and unresolved issues.
Stack management
You can buy tools through 3PS, but the retainer buys judgment.
EDR, email filtering, backup, identity, SASE, SIEM, vulnerability management, and monitoring can be managed as add-ons.
Recovery practice
Backups only count when restore has been validated.
Questions people ask when the room is moving fast.
Short answers first. The details get written into the incident record once the business is stable.
First move
What should we do first?
Call before changing the scene. Preserve evidence, stabilize access, isolate affected systems, protect backups, and decide what should not be touched.
Speed
How fast can 3PS start?
Call to confirm availability, authority, access, and the response engagement. Onsite requirements and timing are confirmed around location, access, and agreed scope.
Cost
What does response cost?
Non-retained emergency response starts at $500/hour with a two-hour minimum. Urgency, travel, hardware, and third-party tools are confirmed before work starts or scope changes.
Evidence
What does leadership get?
An incident brief covering the timeline, scope, evidence, actions taken, restore status, remaining risk, and the controls that reduce repeat failure.
Active incident
If ransomware is happening now, do not wait on a form.
Call to confirm availability and the response engagement. Agree on the immediate priorities, evidence to preserve, access requirements, and whether remote response, onsite response, or both are appropriate.