The earlier archive Written for a different audience — operations teams, business stakeholders, new joiners. It is kept unchanged, with its original date, because a dated body of work says something a rewritten one cannot.

Security Hardening: Not Just an IT Concern

It was September 2018 at i4cus Nigeria Limited. We were working with a healthcare provider who needed to secure their patient management system.


The Wednesday We Almost Lost Everything

It was September 2018 at i4cus Nigeria Limited. We were working with a healthcare provider who needed to secure their patient management system.

The CTO was skeptical. "We've never had a breach. Our systems are fine. Why should we spend money on security hardening?"

I had the data. I had the statistics. I had the horror stories from other healthcare providers who hadn't taken security seriously.

But he wasn't convinced.

Until the day he almost learned the hard way.

The Near-Miss Incident

It was a Wednesday afternoon. One of our developers was monitoring system logs and noticed something unusual:

Multiple failed login attempts from an IP address in Eastern Europe. They were trying different username/password combinations, probing for vulnerabilities.

They hadn't gotten in yet. But they were trying.

We blocked the IP address immediately. We implemented additional rate limiting. We triggered an investigation.

The CTO came to me afterwards, looking shaken.

"They could have gotten in," he said. "They could have accessed patient records. Medical history. Insurance information. Everything."

"Yes," I said quietly. "And if they had, your liability would have been catastrophic. Your reputation would have been destroyed. Your patients would have sued. Your business might not have survived."

He looked at me for a long time.

"How much would this hardening have cost?" he asked.

"$45,000," I said. "Spread over 6 months. Including penetration testing, security audits, and remediation."

He nodded slowly. "A data breach would have cost us millions. In reputation alone."

The Struggle: The "It Won't Happen to Us" Mindset

I want to be honest: this was difficult to navigate.

Security hardening is expensive. It's time-consuming. It feels like you're spending money to prevent problems that might never happen.

And many organizations—especially smaller ones—think like this healthcare provider initially thought:

"We're not a target. We're too small to matter." "We've never had a problem. Why worry now?" "Our systems are behind firewalls. We're safe."

I've seen this mindset across healthcare, education, and commercial environments. It's dangerous.

Because here's the truth: You're not too small to be a target. You're just too small to survive a breach.

The Transformation: Reframing Security as Business Protection

After that near-miss incident, we completely reframed how we talked about security with stakeholders.

We stopped talking about:

  • Encryption protocols
  • Penetration testing methodologies
  • Security frameworks and standards

We started talking about:

  • Patient privacy
  • Regulatory compliance
  • Business continuity
  • Reputation protection

Here's the framework I developed to explain security hardening to non-technical stakeholders:


The Security Hardening Business Case

What Is Security Hardening?

Technical explanation: Implementing security controls, removing vulnerabilities, and following security best practices to protect systems from attacks.

Business explanation: Making it harder for bad actors to access your systems and steal your data. Like adding better locks to your doors and windows—but for your digital assets.

Why It Matters (Business Impact)

1. Regulatory Compliance

Healthcare: GDPR, HIPAA, data protection laws require it. You're legally obligated to protect patient data.

Commercial: PCI-DSS for payment processing. GDPR for customer data. Industry-specific regulations.

The Risk: Non-compliance can mean fines (up to 4% of global revenue under GDPR), legal liability, and loss of business licenses.

2. Patient/Customer Trust

Healthcare: Patients trust you with their most sensitive information. Medical history, mental health, genetic data. If you lose it, you lose their trust forever.

Commercial: Customers trust you with payment information, personal details, purchase history. A breach destroys that trust.

The Risk: Reputation damage can be more expensive than any fine. 60% of small businesses close within 6 months of a cyberattack.

Healthcare: If patient data is breached, you can be sued. Negligence claims. Class action lawsuits.

Commercial: Breached customer data can lead to litigation. Compensation claims. Regulatory penalties.

The Risk: Legal costs can exceed the fine. Defending yourself in court is expensive even if you win.

4. Business Continuity

Ransomware: Modern attacks encrypt your systems and demand payment. You can't operate until you pay (which funds criminals) or restore from backups (which you hope you have).

The Risk: Average downtime from ransomware: 21 days. That's 21 days of zero revenue.

The ROI Calculation for Healthcare Provider

Let me share the actual business case we presented to that skeptical CTO:

Investment: Security Hardening

  • Penetration testing: $15,000
  • Security audit: $10,000
  • Remediation (fixing vulnerabilities): $15,000
  • Employee security training: $5,000

Total Investment: $45,000

Potential Cost of a Breach

Based on IBM's Cost of Data Breach Report (2018 data):

  • Average cost per healthcare record breached: $408
  • If 5,000 patient records are breached (realistic number for medium practice)
  • Direct cost: 5,000 × $408 = $2,040,000

Plus:

  • Regulatory fines: Up to 4% of global revenue (GDPR)
  • Legal fees: $50,000 - $200,000
  • Reputation damage: Incalculable
  • Lost patients: Hard to quantify, but significant

Total Potential Cost: >$2.5 million

ROI Calculation

  • Investment: $45,000
  • Risk avoided: $2,500,000
  • ROI: 5,455%

Even if you assume a breach is unlikely (10% chance per year):

  • Expected cost per year: $250,000
  • Investment per year: $7,500 (amortized over 6 years)
  • ROI: 3,233%

The CTO looked at these numbers for a long time.

"So security hardening isn't an IT expense," he said slowly. "It's insurance."

"Yes," I said. "But better than insurance. Insurance pays you after something bad happens. Security hardening prevents the bad thing from happening in the first place."

The Framework: What We Actually Did

Here's the security hardening framework we implemented:

1. Vulnerability Assessment

  • What: Automated and manual testing to find security weaknesses
  • Why: You can't fix what you don't know is broken
  • Business Value: Identifies your biggest risks first

2. Penetration Testing

  • What: Ethical hackers try to break into your systems (with permission)
  • Why: Real-world attack simulation
  • Business Value: Finds vulnerabilities that automated tools miss

3. Remediation

  • What: Fixing identified vulnerabilities
  • Why: Testing without fixing is useless
  • Business Value: Actually reduces risk

4. Authentication Hardening

  • What: Multi-factor authentication, password policies, account lockouts
  • Why: Weak authentication is the #1 attack vector
  • Business Value: Stops most automated attacks

5. Data Protection

  • What: Encryption at rest and in transit, access controls, audit logging
  • Why: Even if attackers get in, they can't read your data
  • Business Value: Protects your most valuable asset

6. Monitoring & Incident Response

  • What: Security monitoring, alerting, and incident response plan
  • Why: You need to know quickly if something happens
  • Business Value: Reduces breach impact and cost

7. Employee Training

  • What: Security awareness training for all staff
  • Why: 60-70% of breaches involve phishing or social engineering
  • Business Value: Addresses the biggest vulnerability: your people

The Results: What Changed

Security Metrics

  • Before: 12 critical vulnerabilities, 45 high-risk vulnerabilities
  • After: 0 critical vulnerabilities, 2 high-risk vulnerabilities

Security Incidents

  • Before: 2-3 security incidents per month (attempts, probes, minor issues)
  • After: 0 security incidents in 6 months

Compliance Readiness

  • Before: Would fail a GDPR audit in multiple areas
  • After: Would pass a GDPR audit with minor observations

Staff Awareness

  • Before: 40% of staff clicked on phishing emails in simulated attacks
  • After: 5% of staff clicked on phishing emails in simulated attacks

Stakeholder Confidence

  • Before: Leadership skeptical about security investment
  • After: Leadership advocates for security. "Security isn't IT expense. It's business protection."

The Hard Truth I Learned

Here's what this project taught me:

Security isn't an IT project. It's business protection.

I see organizations make the mistake of treating security as a technical initiative. They give it to the IT team. They ask for technical reports. They measure technical metrics.

But security is about:

  • Protecting patient privacy (not just encryption)
  • Maintaining customer trust (not just firewalls)
  • Ensuring business continuity (not just intrusion detection)
  • Complying with regulations (not just access controls)

The most successful security initiatives I've seen are the ones that are owned by the business, not just IT.

A Framework for Stakeholders

If you're trying to convince leadership to invest in security hardening, use this approach:

Step 1: Speak Their Language

Don't talk about "zero-day vulnerabilities" or "SQL injection." Talk about "protecting patient data" and "maintaining customer trust."

Step 2: Calculate the Business Risk

Show the actual cost of a breach. Use real numbers from your industry.

Step 3: Compare Investment to Risk

Show ROI. It's compelling.

Step 4: Frame as Insurance, Not Expense

Insurance is a legitimate business cost. Security hardening is better than insurance—it prevents the need for insurance payout.

Step 5: Make It Business-Owned

Don't make it an IT project. Make it a business initiative with IT support.

Common Objections (And Responses)

Objection 1: "We're too small to be a target"

Response: "You're not too small to be a target. You're just too small to survive a breach. Automated attacks don't care about your size—they scan everyone."

Objection 2: "We've never had a problem"

Response: "You've never had a fire, but you have fire insurance. You've never been sued, but you have liability insurance. Security hardening is the same—you don't wait for the problem to protect against it."

Objection 3: "It's too expensive"

Response: "The cost of security hardening is known: $X. The cost of a breach is unknown, but averages $Y. Would you rather pay the known cost or gamble on the unknown?"

Objection 4: "Our systems are behind firewalls"

Response: "Firewalls are necessary but insufficient. Most attacks come through phishing, compromised credentials, or application vulnerabilities—not through the firewall."

The Inspiration

After implementing security hardening for that healthcare provider, the CTO came to me with a realization.

"You know what I realized?" he said. "Security isn't about fear. It's about care. We're showing our patients that we care enough to protect their information."

That's exactly right.

Security hardening is an act of care. It's saying:

  • We care about your privacy
  • We care about protecting your information
  • We care enough to invest in doing this right

That's not just good business. That's good ethics.


Quick Security Checklist

Security AreaBusiness ImpactPriority Level
Multi-factor AuthenticationStops most automated attacksCritical
Encryption (data at rest)Protects data even if attackers get inCritical
Encryption (data in transit)Prevents interception of sensitive dataCritical
Employee TrainingAddresses #1 attack vector (phishing)Critical
Regular Security AuditsFinds vulnerabilities before attackers doHigh
Penetration TestingReal-world attack simulationHigh
Incident Response PlanReduces breach impact if it happensHigh
Access ControlsLimits damage if credentials are compromisedHigh
Monitoring & AlertingEnables quick response to incidentsMedium
Regular BackupsEnables recovery from ransomware attacksMedium

What's your experience with security hardening? Have you convinced skeptical stakeholders to invest in protection?

#Security #BusinessProtection #RiskManagement #Compliance #CyberSecurity #HealthcareIT

The archive

Every article, 2013–2026

Thirty dated articles on application support, delivery, infrastructure and data — plus the recent writing on CI/CD reproducibility and offline-first design.

The recent work is written for a specialist audience, and it is where the measurement discipline is set out in full.

Recent writingOpen Source Impact