The Scoop on Regulatory Compliance

Akins IT • April 14, 2016
Connect with us

First, what is it? Regulatory compliance means that your business is obeying the state and federal restrictions set in place. These regulations aim to prevent the devastating impacts that can result to both consumers and companies from poor management of sensitive data. 


For most companies, IT is in the spotlight when it comes to compliance and most of these IT departments are given the task of ensuring compliance by their CEO, CFO, CIO, or other director. The reason? Beyond the penalties we'll discuss below, many of these laws carry personal liability for high-ranking corporate officials. 


PCI DSS


This type of regulation applies to companies that deal with credit, meaning they either accept credit card payments or deal with the transfer of information relating to a credit transaction. With identity theft on the rise, failure to comply may lead to the theft of your client's identity. Not only will you have lost their trust, but you will also be likely to have to pay restitution (a reimbursement of the amount taken) in addition to other fines and penalties. 


HIPPA


HIPPA laws are oriented around the protection of an individual's right to privacy in their medical forms. This does not only apply to doctors, but rather applies to every single organization that interacts with this type of sensitive data. The penalties for failing to comply with these mandated restrictions include fines, loss of business license, and in severe cases may even include imprisonment!


SOX


SOX compliance focuses on accuracy in bookkeeping, accounting, and other types of financial reporting. Getting creative on the corporate books is a bad idea. Need more persuading? Take a look at Enron, WorldCom, Tyco International, and Adelphia. They had to learn the hard way. Fortunately for you, we've written a blog. 


The morale of the story? Regardless of the specific regulatory law or industry, the answer remains the same - the cost involved with failing to comply is high and jeopardizes your business. 

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