{"id":15783,"date":"2024-02-23T00:00:00","date_gmt":"2024-02-23T00:00:00","guid":{"rendered":"https:\/\/gascon.ca\/confessions-of-a-cybersecurity-lawyer-on-dodging-deception\/"},"modified":"2024-02-23T00:00:00","modified_gmt":"2024-02-23T00:00:00","slug":"confessions-of-a-cybersecurity-lawyer-on-dodging-deception","status":"publish","type":"post","link":"https:\/\/gascon.ca\/en\/confessions-of-a-cybersecurity-lawyer-on-dodging-deception\/","title":{"rendered":"CONFESSIONS OF A CYBERSECURITY LAWYER ON DODGING DECEPTION"},"content":{"rendered":"

\u201cI would never fall for a scam! I\u2019m smarter than that, it could never happen to me!\u201d\u00a0<\/span><\/i><\/p>\n

 <\/p>\n

As a professional who specializes in cybersecurity and privacy law, I have extensive training on the techniques that threat actors use to obtain sensitive information. I know what the threats are and how to spot them. I\u2019ve learned exactly what to look out for, to never click a link in a suspicious email, to not take candy from strangers\u2026 I\u2019m supposed to be the predator, not the prey. Right? Well, let me tell you about my Tuesday:<\/span><\/p>\n

 <\/p>\n

I spent the day at the office. I went home, spent some time with my kid, fed him some dinner, and sent him off to bed for the night.\u00a0 Then, the phone rang. I picked up, assuming it was the Chinese food place I had just ordered from, calling me back to clarify the extent of my shrimp allergy. Incorrect.\u00a0<\/span><\/p>\n

 <\/p>\n

The caller identified himself as a representative from the fraud department of the bank where my husband and I have our day-to-day accounts. He informed me that there were several suspicious charges on my credit card and that he wanted to review them with me. I said OK. He confirmed who he was speaking to (he knew my name), he confirmed my home address (which he also knew) and then began asking me some questions about my recent whereabouts. Apparently, the bank had flagged transactions on my card from a gas station in Toronto and additional suspicious transactions were starting to come in from all over Toronto.\u00a0<\/span><\/p>\n

 <\/p>\n

And so, the caller and I began the \u201cauthentication process\u201d. Before providing my details, I asked him to confirm the number of the credit card in question. He provided me with the four first digits of my card, that is, the digits which identify all Visa cards issued by our bank. I then asked him to provide me with the last four digits of the credit card, whereupon he told me that this information could not provided until my identity had been authenticated by the bank, via their security questions. This is when my \u201cSpidey senses\u201d started tingling: I did not recognize the number from which this man was calling, nor did I have any actual confirmation that he was, in fact, a representative of the bank\u2019s fraud department.\u00a0\u00a0<\/span><\/p>\n

 <\/p>\n

I expressed my concerns about his identity and explained to him that, as a precaution, I would end this phone call and call back the bank\u2019s fraud department, thus allowing me to ensure that I was speaking to a representative of the bank. He quickly reassured me, explaining that he understood my concern, congratulating me on my vigilance, while reiterating the importance of promptly verifying the suspicious transactions, then cancelling and reissuing a new (safe) credit card. Once again, I insisted that I would end the call and phone the bank back, without delay. His tone began to change. Instead of a professional, customer service veneer, his tone became more insistent: the call was being recorded. My failure to comply with addressing this urgent matter would mean that the suspicious charges would be allowed to go through, and worse, that I would be responsible for paying them if I ended the call, as the bank would have fulfilled their duty to advise me of possibly fraudulent activity and there would be recorded evidence of this. We wouldn\u2019t want that, would we? I needed to provide my information, at once.\u00a0<\/span><\/p>\n

 <\/p>\n

\"hacker<\/p>\n

 <\/p>\n

I suggested that if he felt, as a representative of the bank, that my card was compromised, he had my permission, on recording, to cancel my credit card without delay. I would call back the fraud department and sort… The line went dead. He had ended the call, realizing that I would not be complying with his requests, despite his skilled attempts to dupe me.\u00a0<\/span><\/p>\n

 <\/p>\n

I immediately went into my online banking account and locked all my credit and debit card. I used the number provided on the back of my credit card to call my bank and verify whether there had, in fact, been fraudulent transactions on my account. As it happens, my credit card was clean. No suspicious charges. No cancellation. No record of the fraud department reaching out to me.\u00a0<\/span><\/p>\n

 <\/p>\n

I had almost been a victim of what is commonly referred to as a \u201csocial engineering\u201d attack, a strategy by which threat actors use psychological manipulation to obtain access to sensitive or private information. He already had my name and phone number as well as my physical and email addresses, information easily obtained from a simple data breach suffered by any of the places I shop online. He also correctly assumed that I was in possession of a credit card, but clearly did not have the information he would require to use it himself, which was most likely the reason for the call. The threat actor used \u201cpretexting\u201d, a common social engineering technique, to try and obtain my compliance, identifying himself as a fraud department representative, to gain my trust and lead me to divulge valuable information. He also used the oldest technique in the book: \u201cfear\u201d, threatening me with monetary loss if I did not comply with his request, quickly.\u00a0<\/span><\/p>\n

 <\/p>\n

Had I been just a bit more tired, distracted or otherwise inattentive, I might not have picked up on the cues. But my \u201cmuscle memory\u201d kicked in and I remembered to:\u00a0<\/span><\/p>\n

    \n
  1. Check the source<\/strong> \u2013 I didn\u2019t rely on the threat actor\u2019s assertion that he was from the bank and insisted on communicating with them only through a reliable source.\u00a0<\/span><\/li>\n
  2. Break the loop and slow down<\/strong> \u2013 creating a false sense of urgency means targets are less likely to critically assess the information with which they are being presented. Sometimes taking an extra second to think about the issue (why can\u2019t I just call back in less than a minute? If he has already stopped the charges, why is this so urgent?) allows you to see the attack for what it really is.\u00a0<\/span><\/li>\n
  3. Ask for ID<\/strong> \u2013 make sure the person is who they say they are. Check the phone number online. Ask what their extension number is, so that you can call back if the call is disconnected. If they hesitate to identify themselves, disconnect.\u00a0<\/span><\/li>\n<\/ol>\n

     <\/p>\n

    Even though this attempt failed, I took steps to safeguard my credit and bank accounts, since clearly my personal information is out in the ether. In addition to contacting the fraud department of my bank, I filled a report online with the Canadian Anti Fraud Centre Reporting System (found here: <\/span>https:\/\/www.services.rcmp-grc.gc.ca\/CAFCFRS\/<\/span><\/a>). I also signed up for credit monitoring services with Equifax Canada (<\/span>https:\/\/www.consumer.equifax.ca\/personal<\/span><\/a>) TransUnion (<\/span>https:\/\/www.transunion.ca\/sites\/ca\/home_en<\/span><\/a>).\u00a0<\/span><\/p>\n

     <\/p>\n

    By Alexandra Kallos<\/a><\/p>\n

     <\/p>\n","protected":false},"excerpt":{"rendered":"

    \u201cI would never fall for a scam! I\u2019m smarter than that, it could never happen to me!\u201d\u00a0   As a professional who specializes in cybersecurity and privacy law, I have extensive training on the techniques that threat actors use to obtain sensitive information. I know what the threats are and how to spot them. I\u2019ve […]<\/p>\n","protected":false},"author":1,"featured_media":12511,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[172],"tags":[],"class_list":["post-15783","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-cybersecurity"],"acf":[],"_links":{"self":[{"href":"https:\/\/gascon.ca\/en\/wp-json\/wp\/v2\/posts\/15783","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/gascon.ca\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/gascon.ca\/en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/gascon.ca\/en\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/gascon.ca\/en\/wp-json\/wp\/v2\/comments?post=15783"}],"version-history":[{"count":0,"href":"https:\/\/gascon.ca\/en\/wp-json\/wp\/v2\/posts\/15783\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/gascon.ca\/en\/wp-json\/wp\/v2\/media\/12511"}],"wp:attachment":[{"href":"https:\/\/gascon.ca\/en\/wp-json\/wp\/v2\/media?parent=15783"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/gascon.ca\/en\/wp-json\/wp\/v2\/categories?post=15783"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/gascon.ca\/en\/wp-json\/wp\/v2\/tags?post=15783"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}