SecPod

Learn Search

Search across all Learn content

← Back to Expressions & POVs
What are we doing wrong in safeguarding our computer systems?

What are we doing wrong in safeguarding our computer systems?

1. Naïve Belief: Who is interested in my system? Nobody is going to attack me. I haven’t done anything bad to anyone, so why will they?

May 23, 2013By Chandra1 min read

1. Naïve Belief: Who is interested in my system? Nobody is going to attack me. I haven’t done anything bad to anyone, so why will they?

2. Believing Security can be bought: that magic device that I bought will take care of everything.

3. Trusting Anti-virus is enough to safeguard the system: Feel safe once installed.

4. Cleaning instead of prevention: Trying to clean the malware after it has already infected instead of putting in all the measures that could have avoided the malware infection itself.

5. Ignore proactive security measures:Not proactively assessing the security posture of the system in order to fix the loopholes and strengthening the system.

6. Not willing to take the hard step: patching and hardening is hard to do.

On the last point, yes, it is hard, because,

  • Users are not aware what patches to apply
  • It takes too long to download and install for each application
  • It takes away time from the core work
  • Not aware what the update might do

Hardening the security posture of the system, knowing the loopholes and applying the fix is a very effective and proven defense system. This requires a deeper or may be simpler, second look.

Featured Posts

Open What Is a Software Patch? Patch vs Update Explained
What Is a Software Patch? Patch vs Update Explained

Point of View

What Is a Software Patch? Patch vs Update Explained

A software patch corrects a problem in existing software, while an update can include fixes, reliability changes, or new functionality. See how patches differ from updates and how teams manage them safely.

Sep 28, 2026

Open Patch Management Schedule and Cadence: How Often Should You Patch?
Patch Management Schedule and Cadence: How Often Should You Patch?

Point of View

Patch Management Schedule and Cadence: How Often Should You Patch?

Patch timing should reflect exploit activity, asset exposure, business impact, vendor release cycles, testing needs, and deployment risk. See how teams can set routine and expedited update windows.

Sep 28, 2026

Open Vulnerability Backlog Is not Just A Remediation Problem

Vulnerability Backlog Is not Just A Remediation Problem

Point of View

Vulnerability Backlog Is not Just A Remediation Problem

A growing vulnerability backlog is one of the biggest concerns for security leaders, and it has become even more pressing as AI accelerates vulnerability discovery. When organizations look for ways to reduce that backlog, the focus usually turns to remediation. The reasons are familiar. Patching tak

Sep 21, 2026

Open Application Vulnerability Assessment Explained
Application Vulnerability Assessment Explained

Point of View

Application Vulnerability Assessment Explained

Sep 18, 2026