Automatically forwarding to junk honeypot phishing email addresses belonging to the company?

The name of the pictureThe name of the pictureThe name of the pictureClash Royale CLAN TAG#URR8PPP





.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty margin-bottom:0;







up vote
0
down vote

favorite












Company has honeypot phishing emails from within our organization in microsoft outlook. e.g. hr@companyname.com , ithelpdesk@companyname.com , etc. Having fallen to one of these in a lapse of judgement while working late, I endeavoured to block it, as to not fall for any more of them from that source. I found that I could not block the email as it was from within my organization (it's some outlook admin setting I think).



However I may be able to set certain senders be sent to junk through the "rules" setting, as to save myself time/attention or possible falling for any more traps.



Would automatically sending emails from known honeypot addresses from within my company to junk automatically be a bad idea?



I feel it would be poor taste/execution if the company started legitimately using their previously honeypot email addresses as legitimate emails for important information. I would also expect that important information can be escalated beyond email in person, or through work phone or other channels of communication (company instant messaging, company HR system, etc) The company is somewhat small ~100 people.



I can see a counter argument being that legitimate email addresses belonging to the company can be compromised and bad stuff sent through them. Thus always constant vigilance is important regardless of sender, and I'm not practicing my "security mindfulness) if I just block my known encountered honeypots, because I'm not playing the game.



However with my knowledge and due diligence of these appearing to be dedicated honeypot email addresses (never/not used for anything else), I feel blocking them serves to benefit myself and the company's interests (letting me just work).









share



























    up vote
    0
    down vote

    favorite












    Company has honeypot phishing emails from within our organization in microsoft outlook. e.g. hr@companyname.com , ithelpdesk@companyname.com , etc. Having fallen to one of these in a lapse of judgement while working late, I endeavoured to block it, as to not fall for any more of them from that source. I found that I could not block the email as it was from within my organization (it's some outlook admin setting I think).



    However I may be able to set certain senders be sent to junk through the "rules" setting, as to save myself time/attention or possible falling for any more traps.



    Would automatically sending emails from known honeypot addresses from within my company to junk automatically be a bad idea?



    I feel it would be poor taste/execution if the company started legitimately using their previously honeypot email addresses as legitimate emails for important information. I would also expect that important information can be escalated beyond email in person, or through work phone or other channels of communication (company instant messaging, company HR system, etc) The company is somewhat small ~100 people.



    I can see a counter argument being that legitimate email addresses belonging to the company can be compromised and bad stuff sent through them. Thus always constant vigilance is important regardless of sender, and I'm not practicing my "security mindfulness) if I just block my known encountered honeypots, because I'm not playing the game.



    However with my knowledge and due diligence of these appearing to be dedicated honeypot email addresses (never/not used for anything else), I feel blocking them serves to benefit myself and the company's interests (letting me just work).









    share























      up vote
      0
      down vote

      favorite









      up vote
      0
      down vote

      favorite











      Company has honeypot phishing emails from within our organization in microsoft outlook. e.g. hr@companyname.com , ithelpdesk@companyname.com , etc. Having fallen to one of these in a lapse of judgement while working late, I endeavoured to block it, as to not fall for any more of them from that source. I found that I could not block the email as it was from within my organization (it's some outlook admin setting I think).



      However I may be able to set certain senders be sent to junk through the "rules" setting, as to save myself time/attention or possible falling for any more traps.



      Would automatically sending emails from known honeypot addresses from within my company to junk automatically be a bad idea?



      I feel it would be poor taste/execution if the company started legitimately using their previously honeypot email addresses as legitimate emails for important information. I would also expect that important information can be escalated beyond email in person, or through work phone or other channels of communication (company instant messaging, company HR system, etc) The company is somewhat small ~100 people.



      I can see a counter argument being that legitimate email addresses belonging to the company can be compromised and bad stuff sent through them. Thus always constant vigilance is important regardless of sender, and I'm not practicing my "security mindfulness) if I just block my known encountered honeypots, because I'm not playing the game.



      However with my knowledge and due diligence of these appearing to be dedicated honeypot email addresses (never/not used for anything else), I feel blocking them serves to benefit myself and the company's interests (letting me just work).









      share













      Company has honeypot phishing emails from within our organization in microsoft outlook. e.g. hr@companyname.com , ithelpdesk@companyname.com , etc. Having fallen to one of these in a lapse of judgement while working late, I endeavoured to block it, as to not fall for any more of them from that source. I found that I could not block the email as it was from within my organization (it's some outlook admin setting I think).



      However I may be able to set certain senders be sent to junk through the "rules" setting, as to save myself time/attention or possible falling for any more traps.



      Would automatically sending emails from known honeypot addresses from within my company to junk automatically be a bad idea?



      I feel it would be poor taste/execution if the company started legitimately using their previously honeypot email addresses as legitimate emails for important information. I would also expect that important information can be escalated beyond email in person, or through work phone or other channels of communication (company instant messaging, company HR system, etc) The company is somewhat small ~100 people.



      I can see a counter argument being that legitimate email addresses belonging to the company can be compromised and bad stuff sent through them. Thus always constant vigilance is important regardless of sender, and I'm not practicing my "security mindfulness) if I just block my known encountered honeypots, because I'm not playing the game.



      However with my knowledge and due diligence of these appearing to be dedicated honeypot email addresses (never/not used for anything else), I feel blocking them serves to benefit myself and the company's interests (letting me just work).







      email security





      share












      share










      share



      share










      asked 9 mins ago









      user1821961

      18117




      18117

























          active

          oldest

          votes











          Your Answer







          StackExchange.ready(function()
          var channelOptions =
          tags: "".split(" "),
          id: "423"
          ;
          initTagRenderer("".split(" "), "".split(" "), channelOptions);

          StackExchange.using("externalEditor", function()
          // Have to fire editor after snippets, if snippets enabled
          if (StackExchange.settings.snippets.snippetsEnabled)
          StackExchange.using("snippets", function()
          createEditor();
          );

          else
          createEditor();

          );

          function createEditor()
          StackExchange.prepareEditor(
          heartbeatType: 'answer',
          convertImagesToLinks: false,
          noModals: false,
          showLowRepImageUploadWarning: true,
          reputationToPostImages: null,
          bindNavPrevention: true,
          postfix: "",
          noCode: true, onDemand: true,
          discardSelector: ".discard-answer"
          ,immediatelyShowMarkdownHelp:true
          );



          );













           

          draft saved


          draft discarded


















          StackExchange.ready(
          function ()
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fworkplace.stackexchange.com%2fquestions%2f120137%2fautomatically-forwarding-to-junk-honeypot-phishing-email-addresses-belonging-to%23new-answer', 'question_page');

          );

          Post as a guest



































          active

          oldest

          votes













          active

          oldest

          votes









          active

          oldest

          votes






          active

          oldest

          votes















           

          draft saved


          draft discarded















































           


          draft saved


          draft discarded














          StackExchange.ready(
          function ()
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fworkplace.stackexchange.com%2fquestions%2f120137%2fautomatically-forwarding-to-junk-honeypot-phishing-email-addresses-belonging-to%23new-answer', 'question_page');

          );

          Post as a guest













































































          Comments

          Popular posts from this blog

          What does second last employer means? [closed]

          Installing NextGIS Connect into QGIS 3?

          One-line joke