Kevin Worthington on X

Independent archive of posts by @kworthington.

Total archived posts: 45

@pearsonified I’ve been doing this for many years. Some manual Venmo requests when the client requests. The last time I integrated a site with the PayPal API was in 2010 and it was painful back then. Plus it was a Joomla! (🤮) site.
Reply archive
(7/7)

7. Communication: Inform stakeholders of the incident and any necessary remediation.
Reply archive
(6/7)

6. Lessons Learned: Document the incident and develop strategies to prevent similar incidents in the future.
Reply archive
(5/7)

5. Recovery: Identify any data that has been corrupted or lost and take steps to recover it.
Reply archive
(4/7)

4. Eradication: Remove any malicious code, files, or activities and restore normal system operation.
Reply archive
(3/7)

3. Analysis: Investigate the incident to determine the scope, severity, and root cause.
Reply archive
(2/7)

2. Containment: Isolate affected systems, suspend user accounts, and disable any unauthorized access.
Reply archive
Basic Incident Response plan
(a thread 🧵 1/7)

1. Identification: Identify the source of the incident, the affected systems, user accounts, and any other pertinent information.
archive
This is in no way advice of any kind but I’m bullish on $T (AT&T). Do with that info what you wish and do your own research. #ATT
archive
← Newer
Page 2 of 2