Triage Account Compromise, Phishing, and Device Loss

To triage account compromise phishing identity theft harassment and device loss, protect Uri and others from immediate physical danger, preserve accessible communication, and route threats, missing person, account takeover, exposed passwords or recovery codes, phishing, identity theft, financial fraud, impersonation, harassment, exploitation, nonconsensual content, malware, lost devices, and lost AAC access to the qualified responder. Clinical data collection never delays 911, platform, financial, identity-recovery, safeguarding, or security action.

Define Uri's page-specific decision

To triage account compromise phishing identity theft harassment and device loss, define the person, purpose, device, account, content, audience, authority, access, authentication, privacy, security, supporter, release condition, stop rule, recovery route, and control-return condition. Predeclare who calls 911, the platform, financial institution, identity-recovery route, cybersecurity lead, safeguarding service, or chosen supporter and what each role may access or disclose.

Protect Uri's communication, secrets, and ownership

Uri's support plan keeps AAC, device access, emergency help, private content, credentials, recovery secrets, identity data, and funds protected under the authorized arrangement. Uri's digital-safety triage matrix cannot create account ownership, identity, platform permission, financial authority, cybersecurity, legal consent, or permission to inspect private content.

Build Uri's digital-safety triage matrix

Create one versioned record for the devices, accounts, messages, and community contexts. Include Uri's purposes, emergencies, devices, accounts, content, audiences, ownership, authentication, access, communication, privacy, payments, supporters, restrictions, incidents, recovery, outcomes, missingness, and reassessment evidence. Use a trigger-to-action matrix with immediate danger, device, account, content, information exposed, money at risk, current access, responder, authority, clock, evidence, and handoff.

Validate Uri's counts and evidence

Reproduce nine people times ten actions equals 90, with 75 initial passes, 87 after rehearsal, and three named open actions.

Connect Uri's evidence to a bounded action

The trainer repeats the three failed routes, verifies current platform, financial, emergency, security, and identity-recovery contacts, and withholds only the affected roles.

Work through Uri's example

Nine team members complete ten tabletop decisions each, producing 90 actions. Seventy-five pass initially. After focused rehearsal, 87 pass. Three remain open: one credential-revocation route, one lost-AAC-device handoff, and one immediate-threat escalation. Preserve every planned and eligible unit, device and account version, authority, access, authentication, content and audience, communication, person choice, response, restriction, incident, recovery, repair, and endpoint. This fictional example supplies no account ownership, platform decision, identity determination, security assurance, treatment effect, compliance result, or promised outcome.

Address Uri's main interpretation risk

Eighty-seven of 90 is a tabletop result. It cannot prove account recovery, fraud reversal, data deletion, emergency response, device return, or live performance. Three open actions remain holds. Review immediate danger, account and platform rules, ownership, authentication, accessibility, privacy, security, financial boundaries, communication, supporter response, instruction, restrictions, person priorities, incidents, burden, missingness, and design strength separately.

Set Uri's ABA scope and ethics boundaries

Uri's digital-safety triage matrix uses the CASP public summary only for high-level ABA behavioral-health-treatment scope for autistic people. The current BACB Ethics Code addresses competence, collaboration, consent and assent when applicable, confidentiality, assessment, risk, documentation, and evaluation for covered people. Device, account, platform, identity, cybersecurity, financial, emergency, safeguarding, employment, and legal authority remain with qualified owners.

Use CISA's four practices within Uri's real accounts

CISA Secure Our World emphasizes recognizing and reporting phishing, strong passwords and password managers, multifactor authentication, and prompt software updates. These are general security practices, not permission to access Uri's account, hold credentials, choose an authenticator, or override accessibility. The digital-safety triage matrix records which current service supports each control and who owns it.

Route suspicious messages through verified channels for Uri

The FTC phishing guide explains that deceptive emails and texts may seek passwords, account numbers, or other information. It advises contacting the company through a number or site already known to be real instead of using the message link. Uri's team may teach that bounded check with synthetic messages while leaving incident response, account action, and money decisions to authorized roles.

Use IdentityTheft.gov only after the right classification for Uri

IdentityTheft.gov recovery steps provide an FTC reporting and recovery route for U.S. identity theft, including contact with affected companies and credential changes. That route does not classify every suspicious message or authorize clinical staff to freeze accounts, access credit reports, file as Uri, or control funds. Preserve the person's authority and the qualified recovery owner.

Apply NIST digital-identity terms cautiously for Uri

Final NIST SP 800-63 Revision 4, released in July 2025, covers digital identity proofing, authentication, and federation for government information systems. It is a technical reference, not a universal consumer-account rule or clinical protocol. Uri's actual platform determines supported authenticators and recovery methods; account ownership, accessibility, risk, and delegated help remain separate decisions.

Treat cognitive accessibility as design evidence for Uri

The W3C cognitive-accessibility page distinguishes WCAG standards from supplemental informative guidance and describes needs involving perception, memory, language, attention, comprehension, and error correction. It cannot diagnose Uri, authorize account access, or guarantee usability. Testing for Uri uses the real interface, assistive technology, authentication, timing, and recovery path with the person.

Keep emergency action ahead of digital data for Uri

The National 911 Program says an emergency requiring immediate police, fire, or ambulance assistance belongs with 911 and that call-takers may provide instructions. Local systems differ, and the guidance is U.S.-specific. Uri's team follows qualified responders rather than completing a teaching trial, screenshot, percentage, or routine approval first.

Make digital communication accessible for Uri

The DOJ effective-communication guidance explains that covered entities consider the nature, length, complexity, context, and person's usual communication method. Platforms and account owners can have separate duties. Communication checks in Uri's digital-safety triage matrix cover instructions, authentication, messages, warnings, reports, and recovery explanations while sending provider-access decisions to the responsible entity.

Preserve Uri's AAC and authorship

The ASHA AAC portal says AAC users should always have access to their communication tools or devices. Uri's primary and tested backup communication remain available during login, messaging, support, recovery, compromise, and emergencies. A supporter may facilitate access without supplying Uri's message, consent, audience, account answer, payment choice, or incident report.

Use technology evidence cautiously for Uri

A systematic review of assistive technology for practical skills included 18 studies involving autistic people or people with intellectual disabilities across varied targets and tools. It cannot establish that an app, reminder, password manager, passkey, filter, tracker, communication device, or recovery aid will teach Uri's skill, prevent compromise, generalize, or improve wellbeing.

Choose Uri's next review trigger

Retrain after a device, account, platform, credential, payment method, recovery contact, security event, threat, or Uri communication change. Record the qualified owner, current source, effective date, device and account version, ownership and access state, authentication and recovery arrangement, communication, intervention and restriction authority, implementation check, accessible explanation, complaint route, and reassessment date.

Close Uri's personal-technology plan

Review the digital-safety triage matrix with Uri, the qualified behavior analyst, authorized supporter when applicable, direct team, and specialists named in the manifest. Confirm that emergencies, account and platform decisions, identity, authentication, accessibility, privacy, cybersecurity, communication, assessment, teaching, restrictions, incidents, recovery, and outcomes remain separate; every denominator is reproducible; AAC, authorship, refusal, withdrawal, private content, secrets, funds, and emergency help remain protected; and conclusions stay bounded to sampled conditions. Keep this page draft and noindex until every required review is complete.

How to Triage Account Compromise, Phishing, Identity Theft, Harassment, and Device Loss