<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Member magazine: usage of 3rd party url shorteners in Tech Talk</title>
    <link>https://community.isc2.org/t5/Tech-Talk/Member-magazine-usage-of-3rd-party-url-shorteners/m-p/35101#M2610</link>
    <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I noticed while reading the last member magazine Infosecurity Professional (2020, March/April) that a lot of links are presented like:&lt;/P&gt;&lt;DIV class="page"&gt;&lt;DIV class="layoutArea"&gt;&lt;DIV class="column"&gt;&lt;P&gt;&lt;SPAN&gt;* &lt;A href="http://bit.ly/2TODOfK" target="_blank" rel="noopener"&gt;http://bit.ly/2TODOfK&lt;/A&gt; (article about security.txt)&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;*&amp;nbsp;&lt;/SPAN&gt;&lt;SPAN&gt;&lt;A href="https://bit.ly/2u6k38L" target="_blank" rel="noopener"&gt;https://bit.ly/2u6k38L&lt;/A&gt; (article about first line of defense (humans).&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;While it might be tempting to use these kind of URLs it's strange to actually use them in an Infosecurity Magazine.&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I'd like to share my opinion about this and am interested to see what's yours.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Since not all of these links actually are links (but text) and one needs to type them over, making just the slightest mistake (capital, or reading a letter I as l (good luck, it's i vs L :)) will lead you to a potential page with malware/phishing/content you are not interested in.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I think some of the url-shortner risks might include:&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;1) The readers won't actually get to see the final url, as this is hidden, so the reader can’t check if it’s ok. And I consider that a bad thing.&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;Just think, what you you rather click:&lt;BR /&gt;A) &lt;A href="https://www.isc2.org/info/" target="_blank" rel="noopener"&gt;https://www.isc2.org/info/&lt;/A&gt; or&lt;BR /&gt;B) &lt;A href="http://bit.ly/isc2info" target="_blank" rel="noopener"&gt;http://bit.ly/isc2info&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;2) The readers might get errors when they actually click the shorted url.&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;See for instance &lt;A title="https://blog.sucuri.net/2014/10/bit-ly-blacklisted-by-google-safe-browsing.html" href="https://blog.sucuri.net/2014/10/bit-ly-blacklisted-by-google-safe-browsing.html" target="_blank" rel="nofollow noopener noreferrer"&gt;Securi Blog&lt;/A&gt;&amp;nbsp;or&amp;nbsp;&lt;A href="https://twitter.com/Scott_Helme/status/950472872304226304/photo/1" target="_blank" rel="noopener"&gt;Photo on twitter&lt;/A&gt; for examples of errors that might occur.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;At this current moment bit.ly is marked by&amp;nbsp;&lt;A title="https://transparencyreport.google.com/safe-browsing/search?url=bit.ly" href="https://transparencyreport.google.com/safe-browsing/search?url=bit.ly" target="_blank" rel="nofollow noopener noreferrer"&gt;Google Safebrowsing &lt;/A&gt;.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Most probably there is no (payed) contract with the shortner, or one that does not guarantee the intergrity or availability of the service.&amp;nbsp;The links won’t work if their server is down. In addition, that link might just have changed due to bugs at the shortening service if that’s not guaranteed by them.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;And in the example of bit.ly, that service isn't available on IPv6-only networks.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;3) If you recently received a phishing e-mail, it will probably link to a url-shorting service. So it might be good for the humans doing 'first line of defense' to actually learn not click these shorted (on non-company domain) links.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;4) Interesting bonus: The statistics are open to everybody that has an account and wants to see them, as many&amp;nbsp;url shortners allow a surplused 'plus' (+) or (.info) behind to give everybody access to the statistics.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;5) Funny fact, the first link was even over http. And bit.ly isn't DNSSEC signed.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;This might leave you thinking: why are there so many url-shortners?&lt;BR /&gt;In the past Twitter actually counted URL length. They however stoped doing that years ago.&lt;BR /&gt;On&amp;nbsp;&lt;A title="https://support.twitter.com/articles/78124" href="https://support.twitter.com/articles/78124" target="_blank" rel="nofollow noopener noreferrer"&gt;Twitter Support&lt;/A&gt; you will now read that "A URL of any length will be altered to 23 characters (...)". Not a character more, even if the link is very long.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;But why Infosecurity Pro. uses it in a PDF? No clue, creating a link would be more convenient than actually typing a short url.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;So, that's my opinion. I'm interested to see how the rest of the ISC2 community thinks about this.&lt;/P&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;</description>
    <pubDate>Fri, 24 Apr 2020 20:11:03 GMT</pubDate>
    <dc:creator>William</dc:creator>
    <dc:date>2020-04-24T20:11:03Z</dc:date>
    <item>
      <title>Member magazine: usage of 3rd party url shorteners</title>
      <link>https://community.isc2.org/t5/Tech-Talk/Member-magazine-usage-of-3rd-party-url-shorteners/m-p/35101#M2610</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I noticed while reading the last member magazine Infosecurity Professional (2020, March/April) that a lot of links are presented like:&lt;/P&gt;&lt;DIV class="page"&gt;&lt;DIV class="layoutArea"&gt;&lt;DIV class="column"&gt;&lt;P&gt;&lt;SPAN&gt;* &lt;A href="http://bit.ly/2TODOfK" target="_blank" rel="noopener"&gt;http://bit.ly/2TODOfK&lt;/A&gt; (article about security.txt)&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;*&amp;nbsp;&lt;/SPAN&gt;&lt;SPAN&gt;&lt;A href="https://bit.ly/2u6k38L" target="_blank" rel="noopener"&gt;https://bit.ly/2u6k38L&lt;/A&gt; (article about first line of defense (humans).&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;While it might be tempting to use these kind of URLs it's strange to actually use them in an Infosecurity Magazine.&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I'd like to share my opinion about this and am interested to see what's yours.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Since not all of these links actually are links (but text) and one needs to type them over, making just the slightest mistake (capital, or reading a letter I as l (good luck, it's i vs L :)) will lead you to a potential page with malware/phishing/content you are not interested in.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I think some of the url-shortner risks might include:&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;1) The readers won't actually get to see the final url, as this is hidden, so the reader can’t check if it’s ok. And I consider that a bad thing.&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;Just think, what you you rather click:&lt;BR /&gt;A) &lt;A href="https://www.isc2.org/info/" target="_blank" rel="noopener"&gt;https://www.isc2.org/info/&lt;/A&gt; or&lt;BR /&gt;B) &lt;A href="http://bit.ly/isc2info" target="_blank" rel="noopener"&gt;http://bit.ly/isc2info&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;2) The readers might get errors when they actually click the shorted url.&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;See for instance &lt;A title="https://blog.sucuri.net/2014/10/bit-ly-blacklisted-by-google-safe-browsing.html" href="https://blog.sucuri.net/2014/10/bit-ly-blacklisted-by-google-safe-browsing.html" target="_blank" rel="nofollow noopener noreferrer"&gt;Securi Blog&lt;/A&gt;&amp;nbsp;or&amp;nbsp;&lt;A href="https://twitter.com/Scott_Helme/status/950472872304226304/photo/1" target="_blank" rel="noopener"&gt;Photo on twitter&lt;/A&gt; for examples of errors that might occur.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;At this current moment bit.ly is marked by&amp;nbsp;&lt;A title="https://transparencyreport.google.com/safe-browsing/search?url=bit.ly" href="https://transparencyreport.google.com/safe-browsing/search?url=bit.ly" target="_blank" rel="nofollow noopener noreferrer"&gt;Google Safebrowsing &lt;/A&gt;.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Most probably there is no (payed) contract with the shortner, or one that does not guarantee the intergrity or availability of the service.&amp;nbsp;The links won’t work if their server is down. In addition, that link might just have changed due to bugs at the shortening service if that’s not guaranteed by them.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;And in the example of bit.ly, that service isn't available on IPv6-only networks.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;3) If you recently received a phishing e-mail, it will probably link to a url-shorting service. So it might be good for the humans doing 'first line of defense' to actually learn not click these shorted (on non-company domain) links.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;4) Interesting bonus: The statistics are open to everybody that has an account and wants to see them, as many&amp;nbsp;url shortners allow a surplused 'plus' (+) or (.info) behind to give everybody access to the statistics.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;5) Funny fact, the first link was even over http. And bit.ly isn't DNSSEC signed.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;This might leave you thinking: why are there so many url-shortners?&lt;BR /&gt;In the past Twitter actually counted URL length. They however stoped doing that years ago.&lt;BR /&gt;On&amp;nbsp;&lt;A title="https://support.twitter.com/articles/78124" href="https://support.twitter.com/articles/78124" target="_blank" rel="nofollow noopener noreferrer"&gt;Twitter Support&lt;/A&gt; you will now read that "A URL of any length will be altered to 23 characters (...)". Not a character more, even if the link is very long.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;But why Infosecurity Pro. uses it in a PDF? No clue, creating a link would be more convenient than actually typing a short url.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;So, that's my opinion. I'm interested to see how the rest of the ISC2 community thinks about this.&lt;/P&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;</description>
      <pubDate>Fri, 24 Apr 2020 20:11:03 GMT</pubDate>
      <guid>https://community.isc2.org/t5/Tech-Talk/Member-magazine-usage-of-3rd-party-url-shorteners/m-p/35101#M2610</guid>
      <dc:creator>William</dc:creator>
      <dc:date>2020-04-24T20:11:03Z</dc:date>
    </item>
    <item>
      <title>Re: Member magazine: usage of 3rd party url shorteners</title>
      <link>https://community.isc2.org/t5/Tech-Talk/Member-magazine-usage-of-3rd-party-url-shorteners/m-p/35103#M2611</link>
      <description>&lt;P&gt;Bitly does seem to be an editorial decision, seeing as it first appeared in Mar/Apr and is widely spread throughout.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I'm not a big fan of&amp;nbsp;any technology that hides the intended action from the user, such as "randomized" URL shorteners.&amp;nbsp; &lt;SPAN&gt;Lots of companies have branded permalink systems that probably would fit the bill better for ISP Magazine, including &lt;A href="https://support.bitly.com/hc/en-us/articles/115001626408-What-is-a-custom-branded-link-" target="_blank" rel="noopener"&gt;bit.ly&lt;/A&gt;. This would allow them to for example use &lt;A href="https://go.isc2.org/ISP-" target="_blank" rel="noopener"&gt;https://go.isc2.org/ISP-&lt;/A&gt;&lt;/SPAN&gt;&lt;SPAN&gt;Mar2020-2901.&amp;nbsp; For the cost of only a dozen more characters, it inspires confidence that&lt;/SPAN&gt;&lt;SPAN&gt;:&lt;/SPAN&gt;&lt;/P&gt;&lt;OL&gt;&lt;LI&gt;&lt;SPAN&gt;It is an (ISC)²-approved link.&lt;/SPAN&gt;&lt;/LI&gt;&lt;LI&gt;&lt;SPAN&gt;It is intended for with the March, 2020 issue of ISP magazine.&lt;/SPAN&gt;&lt;/LI&gt;&lt;LI&gt;&lt;SPAN&gt;It is the first link on page 29.&lt;/SPAN&gt;&lt;/LI&gt;&lt;/OL&gt;&lt;P&gt;&lt;FONT face="inherit"&gt;I do note that &lt;/FONT&gt;&lt;A href="https://groups.io/g/cisspforum/topics" target="_blank" rel="noopener"&gt;CISSP forum&lt;/A&gt;&lt;FONT face="inherit"&gt;&amp;nbsp;also uses 3rd party shorteners in its messages.&amp;nbsp; The excuse there is that the environment is fundamentally text-only and word-wrap tends to break long URLs.&amp;nbsp; Even then, I do not follow URLs that have been &lt;/FONT&gt;obfuscated&lt;FONT face="inherit"&gt;.&amp;nbsp; Perhaps it is my loss, but is is also my risk decision.&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Sat, 25 Apr 2020 03:08:55 GMT</pubDate>
      <guid>https://community.isc2.org/t5/Tech-Talk/Member-magazine-usage-of-3rd-party-url-shorteners/m-p/35103#M2611</guid>
      <dc:creator>denbesten</dc:creator>
      <dc:date>2020-04-25T03:08:55Z</dc:date>
    </item>
    <item>
      <title>Re: Member magazine: usage of 3rd party url shorteners</title>
      <link>https://community.isc2.org/t5/Tech-Talk/Member-magazine-usage-of-3rd-party-url-shorteners/m-p/35109#M2612</link>
      <description>&lt;P&gt;I don't know about bit.ly (which I think first began appearing as a Twitter aid) but the granddaddy of shorteners, TinyURL, provides both a direct link and a preview version to allow inspection of the target url.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Compare&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;A href="https://tinyurl.com/y7s7s24h" target="_blank" rel="noopener"&gt;https://tinyurl.com/y7s7s24h&amp;nbsp;&lt;/A&gt;&lt;/P&gt;&lt;P&gt;and&lt;/P&gt;&lt;P&gt;&lt;A href="https://preview.tinyurl.com/y7s7s24h" target="_blank" rel="noopener"&gt;https://preview.tinyurl.com/y7s7s24h&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Also, notice the format; you can turn any standard TinyURL into a preview version manually.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Craig&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Sat, 25 Apr 2020 15:12:56 GMT</pubDate>
      <guid>https://community.isc2.org/t5/Tech-Talk/Member-magazine-usage-of-3rd-party-url-shorteners/m-p/35109#M2612</guid>
      <dc:creator>CraginS</dc:creator>
      <dc:date>2020-04-25T15:12:56Z</dc:date>
    </item>
    <item>
      <title>Re: Member magazine: usage of 3rd party url shorteners</title>
      <link>https://community.isc2.org/t5/Tech-Talk/Member-magazine-usage-of-3rd-party-url-shorteners/m-p/35115#M2613</link>
      <description>&lt;P&gt;That 'preview' option is a really nice service by TinyURL. Though I noticed you need to load almost every advertising network that exists on the page, and most of the concerns al still valid.&lt;BR /&gt;&lt;BR /&gt;Bit.ly hasn't got that feature, only the + to see the url (and the stats).&lt;BR /&gt;&lt;BR /&gt;Still, for the magazine: having a company-owned shortner (if the url really needs to be seen as text) as suggested by denbesten for this purpose seems a better idea. Might even just use that feature, without loading facebook, google, amazon, yahoo, etc. &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;&lt;/P&gt;</description>
      <pubDate>Sat, 25 Apr 2020 19:27:54 GMT</pubDate>
      <guid>https://community.isc2.org/t5/Tech-Talk/Member-magazine-usage-of-3rd-party-url-shorteners/m-p/35115#M2613</guid>
      <dc:creator>William</dc:creator>
      <dc:date>2020-04-25T19:27:54Z</dc:date>
    </item>
  </channel>
</rss>

