Phishing Attacks and How It Affects Your Organization

Akins IT • February 3, 2020
Connect with us

WHAT IS PHISHING? 


Phishing is an attack on individuals in an attempt to steal sensitive information through emails, websites, text messages or other forms of electronic communication that often look to be official communication from a legitimate company or individual. ​The information these cybercriminals attempt to steal can be user names, passwords, credit card details, bank account information or other credentials.​ Attackers can then use stolen information for malicious purposes, such as hacking, identity theft, or stealing money directly from bank accounts and credit cards. In some cases, they even sell this stolen information in cybercriminal underground marketplaces​.


HOW DOES IT WORK?


Phishing attacks often use social engineering bait or lure content. ​For an organization, a successful phishing attack typically entails discovery and planning by collecting what information is available publicly on the company website, social media, or even domain records such as SPF and MX records.​ This may allow a cybercriminal to articulate the following:


  • the naming scheme in an organization for users accounts
  • high ranking officials
  • what email security solution is being utilized
  • what vendors are being used internally. ​


A cybercriminal will then move to trial and error, where they begin to determine what users may expect on a day to day basis and monitor the results of their fraudulent emails. ​Most commonly, its legitimate-looking communication (usually email) that links to a phishing site mimicking sign-in pages that require users to input login credentials and/or account information. The phishing site then captures the sensitive information as soon as the user provides it, giving attackers access to the information. ​Once they have garnered any level of access they will use this to either initiate an attack or gather additional information to create a even more devised attack. ​


WHAT ARE SOME COMMON TYPES OF PHISHING TECHNIQUES USED AGAINST ORGANIZATIONS?​


  • Whaling – A form of phishing in which the attack is directed at high-level or senior executives within organizations. The content could be written as legal subpoena, customer complaints, or other executive issues​.
  • Impersonation – Where a cybercriminal may attempt to create an email that looks like it is being sent from the CEO, CFO, or other important employees in the organization. Usually the email will request for a specific task to be preformed or access to a specific document.
  • Spear Phishing – A targeted phishing attack involving highly customized lure content towards a specific organization. This socially engineered email would be designed to lure you into opening documents or clicking links that automatically install malware. ​
  • Phishing – A board, automated attack that is less sophisticated or targeted. Its intentions are to send out as many emails, to as many domains as possible and monitor for any results.​


VERIZON'S 2019 DATA BREACH INVESTIGATIONS REPORT


This is the annual analysis of security events impacting organizations around the globe. This is the 12th edition of this report which contains comprehensive summary of data breaches that were reported by public and private entities around the globe. 

Report highlights:​


  • 43% of cyberattacks were on small businesses​
  • C-Suite executives are 12 times more likely to be targeted in social engineering attacks than other employees​
  • Phishing is involved in 32% of breaches and 78% of cyber-espionage incidents​
  • 90% of malware arrives via email​
  • Ransomware is the second biggest malware threat and accounted for 24% of malware-related breaches​


These highlights are important because it shows the vulnerability for cybercriminals to target organizations who don’t have an appropriate solution in place. The solutions that we are discussing in future blogs and webinar videos provide protection against data breaches and phishing overall. 

By Shawn Akins October 20, 2025
October 20, 2025 — Early today, Amazon Web Services experienced a major incident centered in its US‑EAST‑1 (N. Virginia) region. AWS reports the event began around 12:11 a.m. PT and tied back to DNS resolution affecting DynamoDB , with mitigation within a couple of hours and recovery continuing thereafter. As the outage rippled, popular services like Snapchat, Venmo, Ring, Roblox, Fortnite , and even some Amazon properties saw disruptions before recovering. If your apps or data are anchored to a single cloud, a morning like this can turn into a help‑desk fire drill. A multi‑cloud or cloud‑smart approach helps you ride through these moments with minimal end‑user impact. What happened (and why it matters) Single‑region fragility: US‑EAST‑1 is massive—and when it sneezes, the internet catches a cold. Incidents here have a history of wide blast radius. Shared dependencies: DNS issues to core services (like DynamoDB endpoints) can cascade across workloads that never directly “touch” that service. Multi‑cloud: practical resilience, not buzzwords For mid‑sized orgs, schools, and local government, multi‑cloud doesn’t have to mean “every app in every cloud.” It means thoughtful redundancy where it counts : Multi‑region or multi‑provider failover for critical apps Run active/standby across AWS and Azure (or another provider), or at least across two AWS regions with automated failover. Start with citizen‑facing portals, SIS/LMS access, emergency comms, and payment gateways. Portable platforms Use Kubernetes and containers, keep state externalized, and standardize infra with Terraform/Ansible so you can redeploy fast when a region (or a provider) wobbles. (Today’s DNS hiccup is exactly the kind of scenario this protects against.) Resilient data layers Replicate data asynchronously across clouds/regions; choose databases with cross‑region failover and test RPO/RTO quarterly. If you rely on a managed database tied to one region, design an escape hatch. Traffic and identity that float Use global traffic managers/DNS to shift users automatically; keep identity (MFA/SSO) highly available and not hard‑wired to a single provider’s control plane. Run the playbook Document health checks, automated cutover, and comms templates. Then practice —tabletops and live failovers. Many services today recovered within hours, but only teams with rehearsed playbooks avoided user‑visible downtime. The bottom line Cloud concentration risk is real. Outages will happen—what matters is whether your constituents, students, and staff feel it. A pragmatic multi‑cloud stance limits the blast radius and keeps your mission‑critical services online when one provider has a bad day. Need a resilience check? Akins IT can help you prioritize which systems should be multi‑cloud, design the right level of redundancy, and validate your failover plan—without overspending. Let’s start with a quick, 30‑minute review of your most critical services and RPO/RTO targets. (No slideware, just actionable next steps.)
By Shawn Akins October 13, 2025
How a Zero-Day in GoAnywhere MFT Sparked a Ransomware Wave—and What Mid-Sized IT Leaders Must Do Now
By Shawn Akins October 13, 2025
The clock is ticking: Learn your options for Windows 11 migration, Extended Security Updates, and cost‑smart strategies before support ends.
More Posts