Hacker News new | past | comments | ask | show | jobs | submit login

The fact that someone bothered to scan the entire range (or find your port at random) might indicate that they're specifically targeting you, and just being aware of that is an upside.



>and just being aware of that is an upside.

but what can you realistically do with that knowledge?


Infinitely more than you can do without that knowledge


Give some examples then. Knowing that someone is targetting you shouldn’t change anything, you should be ready regardless.


It shouldn't, but it does. Many smaller companies driven by business people, where maybe tech is just seen as a necessity on the side need a narrative like "people are trying to get in and if they do it's going to be a disaster" to take security seriously. Then or at the point where the disaster strikes.

I'm not really sure why this point was voted down below either; just because you work for someone who takes security seriously (at least to the point where it's insurance-satisfyingly safe) does not mean everyone does.

Years ago I worked at a small agency and every bit of time I spent had to be justified and produce tangible/visible results. "But is anyone really going to try to hack this local business" was a question I actually had to answer, since most other employees were creatives.


Argue for more security budget with management. If you can make this sound dramatic enough...




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: