Nice big old port scan. Brand new server too. Just a few days old so there is nothing to find. Don’t worry I contacted AWS. Stay safe out there.

  • MightBeFluffy@pawb.socialOPEnglish
    241·
    1 day ago

    I don’t have any open ports. I do not care if I did. Port scanning is not authorized traffic.

    I would love to see the support request from AWS for this.

    Here you go:

    Mandiant ASM scanners perform a variety of security-related data-gathering tasks, all intended to positively identify assets and their security posture. The gathered information is analyzed by our research team and proactively published to the owners of this information through our freemium product. No Collection task performed requires authorized access. It is intentionally designed to be light. While your IDS or WAF may have alerted on these scans, these are benign flags and are not indicative of malicious behavior.

    If you have further questions, or would like to opt-out, please reply to this message and you will be routed to the appropriate team.

      • cellardoor@lemmy.worldEnglish
        30·
        1 day ago

        I think they have a LOT to learn about how the internet ‘works’ as well as how the internet works.

        • irmadlad@lemmy.worldEnglish
          10·
          1 day ago

          Thing is, for the average consumer of the internet, they have no real concept what’s going on behind the webpage with the fancy graphics they happen to be looking at. When I try to explain to them that bots comprise conservatively 40-50% of all internet traffic which is about ~2 zettabytes per 24 hour period, they still don’t get it. And really, they don’t have to, that’s the job of sysadmin. It’s still pretty mind blowing.

        • sidelove@lemmy.worldEnglish
          25·
          1 day ago

          Bro. AWS can do jack shit, that’s not how it works. You might as well call Toyota next time you see a Camry speeding. All you’re going to do is annoy people who in no way can help you with a problem that is your responsibility. I can guarantee they’ll tell you you should use private VPCs and entrypoints with security groups, which is what every AWS tutorial starts out by telling you to use.

    • ramble81@lemmy.zipEnglish
      21·
      1 day ago

      In other words their response was “hey dumbass here’s what happened, now move along”. They didn’t do anything except school you.

      • MightBeFluffy@pawb.socialOPEnglish
        421·
        1 day ago

        Dude there is a weird disconnect going on in the comments. Yes bots are thing, yes services are abused, yes not everyone plays nice on the Internet, yes you can’t control what traffic comes in. I know I’m going to be seeing more this and yes I’m obviously not going to be responding to every one of them.

        It was my brand new server’s first and I felt like celebrating the event by filling out the AWS abuse form. It was literally copy and paste.

        Also, I’m not fussed about what ever services they are running. I didn’t ask for it or want it. I told them as much and I going to leave it at that.

        No one got schooled. There is nothing wrong with telling someone who shows up at your business to please don’t come back. Y’all need to chill.

        Well this whole thing was fun but I’m going to get on with my day

        • non_burglar@lemmy.worldEnglish
          25·
          1 day ago

          I don’t think anyone here disagrees that port scanning is bad, nor that you even filed an aws ticket. And congrats on your live service.

          But your answers to comments are weird, like this is not only your first server or vps experience with a public interface, but your first time exposing anything to the public web. And even if that’s true, there’s a first time for everyone.

          But man, doubling down and insisting that “port scanning is unauthorized traffic” betrays a certain naivete about how tcpip works.

          What you are seeing is not only normal, but AWS can’t do anything about it because that’s how IP source and destination sockets work.

    • non_burglar@lemmy.worldEnglish
      182·
      1 day ago

      Port scanning is not authorized traffic.

      Lol what

      I think you should read the terms of your AWS contract. How do you think aws moves instances if not for agents gathering metrics?

      And this case is Mandiant, so you’re fine.

      Are you sure you’re ready for AWS?

    • TheKMAP@lemmynsfw.comEnglish
      2·
      1 day ago

      You have bad takes, so my recommendation is to not block Mandiant ASM so that they are able to find stuff, if you mess up.