Mobile app version of vmapp.org
Login or Join
Ogunnowo487

: Intellectual Property theft from our webserver. What should we do? So we caught some computers trying to download a ton of files from our webserver, and we stopped them before they got much

@Ogunnowo487

Posted in: #Data #Security

So we caught some computers trying to download a ton of files from our webserver, and we stopped them before they got much (used iptables to drop their IPs). These were not web crawlers, but scripts that had been written to target a specific data set on our servers.

Has anyone had success in actually tracking down and getting authorities or ISPs to do anything about this kind of thing? If so, please post your suggestions.

Basically I have these IP addresses of the computers that were accessing our servers, they are owned by, surprisingly, a very very large Software company in Washington state. So maybe a rogue worker there or maybe somebody just on their network. I've tried to contact this company, but haven't gotten very far there. Maybe they'll get back to me.

What is the best course of action? Contact the local police where the source IPs are from? Somehow I doubt that will be very effective. But I'm open to advice. What about the FBI, I mean this might be small potatoes for them, but it does involve a large US corp. Anyone try this route?

EDIT: Please assume for sake of argument, that they Hacked into our servers. Let's not get into the whole discussion of "Well you had the data out there, so they didn't steal it", that really misses the point. You can even imagine it was a denial of service attack. You have their IP addresses, they are from a US corp. What do you do??

10.03% popularity Vote Up Vote Down


Login to follow query

More posts by @Ogunnowo487

3 Comments

Sorted by latest first Latest Oldest Best

 

@Gonzalez347

Remove the content in question from public access.

*poof* your problem is solved.

10% popularity Vote Up Vote Down


 

@Murphy175

Get a postal address for the large corporation. Try to get a name for some sysadmin person. Send a calm, polite, letter, saying what happened, when it happened, and that you're unhappy. Include short snippets of logs.

OR:

You know what was downloaded. Now you just need to keep web-searching. As soon as it hits a website you can use copyright laws to have the information taken down. Again, if it ends up on some big company's website a short polite email with details could work wonders.

As others have said; it's hard give an answer without any details. What was downloaded? Image files? Databases? Source code?

10% popularity Vote Up Vote Down


 

@Sarah324

As always: I am not a lawyer.

If you're in the United States this would fall under the FBI's jurisdiction unless you can verify the attack originated within the same state as you and your server is also in the same state.

If the website under attack involved a large corporation you might have some luck in getting the FBI to investigate. Especially if the content being targeted had significant value (i.e. anything that a foreign government might want, anything that can hurt the country in some way, etc). However, if the content is just valuable in terms of monetary value, or does not meet any of the above criteria, you'll be hard pressed to get the FBI's attention due to terrorism and cyber warfare being much higher priorities and monopolizing FBI resources.

Practically speaking, the best you can do is continue to monitor the activity and enact countermeasures to thwart it. If possible, gather as much information about the attacks as you can. If the attacks appear to be part of a larger gambit (other large US companies
are being attacked in a identical fashion) then you can assist any investigation into the matter by the appropriate authorities.

(I used to work for a company that had its server hacked to send out spam. We were able to positively identify who did it but the FBI said since 9/11 incidents like that just aren't even on the radar for them.)

10% popularity Vote Up Vote Down


Back to top | Use Dark Theme