1
“Set it and Forget it” AI Implementation
Many businesses are plugging AI into workflows without clear governance. The risk has shifted
from simply missing out on AI to exposing internal data, allowing shadow AI across teams,
introducing data poisoning, and accepting insecure AI-assisted output into daily operations.
If employees use unmanaged large language models for coding, documentation, content creation,
or customer communication, they may leak proprietary logic, client information, business
processes, or internal development details without realizing it.
Watch for:
Shadow AI, browser-based LLM use without approval, prompt leakage, and insecure AI-generated
code in WordPress, Oxygen, or custom projects.
Better approach:
Create AI governance, approved tools, role-based access, content review processes, and data
handling rules before AI is widely adopted.
2
Neglecting Clean Identity Management
Relying on legacy MFA methods such as SMS codes or simple push approvals is no longer enough.
Attackers increasingly use phishing kits, session theft, and MFA fatigue to compromise
business accounts.
Clean identity management now requires stronger login controls, device trust, access review,
stale account cleanup, and phishing-resistant authentication methods.
Watch for:
FIDO2 security keys, passwordless sign-in, and Conditional Access policies in Intune or
Entra that require a compliant device before access is granted.
Better approach:
Reduce privilege sprawl, remove unused accounts, enforce device compliance, and move toward
phishing-resistant authentication.
3
Underestimating Technical Debt in No-Code and Low-Code
Tools such as WordPress page builders, Oxygen, Breakdance, and other no-code or low-code
systems make website creation faster, but they can also produce plugin bloat, heavy DOM
structures, extra CSS and JavaScript, and long-term maintenance overhead.
This matters because slow websites lose leads, reduce conversions, hurt user experience, and
make advertising more expensive. For SEO, performance is not optional. Lean pages are easier
for users and search engines to trust.
Watch for:
Performance degradation, poor Core Web Vitals, unused elements, excessive scripts, and
oversized page structures.
Better approach:
Keep WordPress builds lean, disable unused builder elements, reduce plugin count, compress
assets, and simplify templates wherever possible.
4
Fragmented Device Management and BYOD Chaos
Allowing personal devices to access SharePoint, Teams, email, and business data without a
proper Mobile Device Management layer creates a major security gap. Unmanaged devices often
lack encryption, patching, compliance policies, and a reliable way to remove company data.
Watch for:
Devices connecting without enrollment, no remote wipe capability, weak PIN policies, and no
proof of encryption or patch status.
Better approach:
Enroll business-accessing devices in Microsoft Intune or a similar MDM solution and require
compliance before access to business data.
5
Ignoring Backup for Cloud SaaS
A common myth is that Microsoft fully backs up Microsoft 365 data for every business need.
In reality, availability is not the same as long-term point-in-time recovery. Deleted or
corrupted data, ransomware events, sync issues, or retention gaps can leave businesses with
fewer recovery options than expected.
Watch for:
SaaS-targeting ransomware, accidental deletion, limited recovery windows, and missing restore
testing for Exchange, OneDrive, and SharePoint.
Better approach:
Use a third-party SaaS backup solution and test restoration regularly so recovery is proven,
not assumed.
6
Poor DNS Governance
DNS is often overlooked, yet poor DNS governance can create serious security and uptime
issues. Giving developers or multiple staff members full DNS access increases the likelihood
of misconfigurations, abandoned subdomains, and forgotten records that can be exploited.
Watch for:
Subdomain takeovers, stale A records, abandoned CNAMEs, old development environments, and
undocumented DNS changes.
Better approach:
Restrict access, audit records regularly, document every change, and clean up unused dev or
staging entries before they become attack paths.
7
Over-Reliance on Single-Vendor Security
Relying on a single vendor for all security functions may simplify procurement, but it also
creates concentration risk. No ecosystem catches everything. If one layer fails, there may
be no compensating control in place.
Watch for:
Gaps in email protection, endpoint visibility, network monitoring, and alert validation
caused by depending entirely on one stack.
Better approach:
Use layered security with endpoint protection, network controls, external filtering, logging,
and segmented defenses across different control points.
8
Treating Cyber Insurance as a Strategy
Cyber insurance is not a replacement for solid IT operations. Many insurers now expect
documented patching, access controls, policy enforcement, device management, and recovery
readiness before they approve claims or set favorable premiums.
Watch for:
Missing patch logs, inconsistent updates, undocumented policies, and poor evidence that
security controls are actually enforced.
Better approach:
Keep automated patching active, document controls, retain logs, and make your security
posture measurable and auditable.
9
Mismanaging Remote Work Connectivity
Traditional VPN-only access models are increasingly seen as legacy architecture. The issue
is not remote work itself. The issue is extending broad network access without validating the
user, device health, and access context each time.
Watch for:
VPN sprawl, always-on trust, unmanaged endpoints, and missing health checks before
connection.
Better approach:
Move toward Zero Trust Network Access with policies that verify the user, device compliance,
and connection context before business access is granted.
10
Ignoring Green IT and E-Waste
Hardware decisions now carry cost, compliance, and sustainability implications. Poor disposal
practices, rapid replacement cycles, and undocumented recycling processes can create data
exposure and unnecessary expense.
Watch for:
No formal disposal policy, missing asset records, no certified recycling partner, and
hardware purchased without lifecycle planning.
Better approach:
Build a hardware lifecycle plan, document disposal, work with recycling partners, and choose
repairable or modular equipment where practical.