Ask HN: Anonymous person sent proof of SSH access to our production server
Came across your question moments after facilitating a security incident dry run for a SaaS with a 6 or 7 person core team (and a lot of sensitive data). Since many of the responses are focusing on the technical and reward&#x2F;ransom aspect of this, I figured I could offer you some parallel thoughts on how to handle this from the business and liability standpoint.<p>There is quite a bit in this response, so please don&#x27;t hesitate to ask if you want to talk this through directly. I can stand to offer 30min to provide some connections and make sure you feel equipped to go it with your current team. No cost of course and no nagging to get you on as a paying customer!<p>1. Insurance - 
Assuming you have a policy geared toward technology companies, you may have coverage for &quot;cyber&quot; incidents. Look at your policy or call your broker to find out how to initiate coverage.<p>a) You probably need to tell them sooner rather than later that you are investigating an incident. 
b) Ask for a referrals to the following specialities: tech&#x2F;privacy law, forensics or security operations, and breach resolution vendors.
c) Find out whether the policy requires you to obtain a referral to use paneled providers (most do from my experience).
d) Find out any other requirements that might determine your ability for coverage down the line.<p>2. Legal (assuming American or similar legal system) -
Given what I know about your situation, I&#x27;d suggest that you retain a lawyer experience with security and breach response. This doesn&#x27;t have to break the bank. The key point is to establish privilege and get help from someone who can navigate the statutory&#x2F;liability landscape (it&#x27;s a shit show). I can recommend one or two that are sensitive to the needs of small business clients.<p>3. Forensics -
If you have insurance coverage that will apply to this scenario, there is little reason not to contact a forensic or security specialist to validate your cleanup and ensure that the infrastructure is totally buttoned down going forward. Definitely follow the rest of this thread and digest the recommendations you&#x27;re getting.<p>4. Customers&#x2F; Stakeholders -
Your customers and stakeholders will appreciate clear communication, whether during the investigation&#x2F;response or after the matter. The lawyer I mentioned above will be able to help you think about communication with these parties as well as timing. If the incident turns into something more than it is right now, you&#x27;ll be thankful for thinking this dimension through carefully.<p>5. Intruder -
Don&#x27;t react carelessly. You don&#x27;t know their motives or further plans. Is this a gray hat who is just wanting you to shore up your system. I&#x27;d be inclined to work with them and possibly even offer a reward. But I wouldn&#x27;t go there without consulting legal counsel. Is this more about taunting or warming you up for a ransom request? Then get some folks with experience in your corner from the start. And be aware, your insurance might even cover a ransom request.<p>6. Law Enforcement -
Most of us prefer not to go here, but keep it as an option. Talk to your attorney about it.<p>7. Documentation -
Start keeping detailed notes. What are the steps you&#x27;re taking to assess the situation? Who are you consulting? How are you measuring the risk? How are you preventing further damage? A breach coach can help you ask the right questions and record the information most needed to protect you and your customers.<p>8. Notification -
If you&#x27;re in the US or EU, you very likely have breach notification requirements. Unless you are certain the intruder did not take or view any protected data (pretty much anything personal or payment related), I would treat the incident as a breach. In the US, you have 47 different state laws dictating notification requirements plus a few federal. Breach resolution services to the rescue if you have insurance. Breach coaches and lawyers may handle the little cases themselves.<p>9. Follow up -
a) Summarize the process in a short report and keep it in case you discover related damage down the line (or get sued).
b) Close the incident out with insurance and provide any documentation they need to process the claim.
c) Put a basic, written, practical plan together.
d) Build a relationship with a knowledgeable insurance broker (I can recommend a few).
e) Review, or update your insurance policy (or buy one).
f) If you can afford it, keep a tech attorney on retainer.
g) Set up a bug bounty through an established program (and if this intruder is well-intentioned, encourage them to use it in the future)