Blog
Practical articles on security, deployment, and evidence.

Dates identify publication on LinkedIn or a future scheduled or planned LinkedIn release. All full articles are available to read now.
Personal perspectives
Philip Lieberman

Published on LinkedIn
Your Audit Is Eating Engineering
How many engineering days disappear into audit preparation without ever showing up in the audit budget?

Published on LinkedIn
One Password. Everyone’s Admin.
If five people know the admin password, which one made the change? That's an awkward question to discover you can't answer after something breaks.

Scheduled on LinkedIn
Rotate a Password. Break Production.
Changing a compromised service password can stop the very systems you're trying to protect.

Scheduled on LinkedIn
Evidence Exists. Where Is It?
Your organization can have the evidence and still spend days hunting for it.

Scheduled on LinkedIn
Employee Gone. Access Remains.
Removing an employee from HR's roster doesn't remove their privileged access everywhere else.

Scheduled on LinkedIn
Trained on the Wrong Policy?
Every employee can appear as ‘trained’ while the record fails to show who acknowledged the current procedure.

Scheduled on LinkedIn
Fixed? Prove It.
A repair command can succeed while the security setting stays wrong.

Scheduled on LinkedIn
Bought the Kit. Who Runs It?
A long feature list can hide an expensive question: who does the remaining work? Learn what a capability does, assists with, or records.

Scheduled on LinkedIn
Tenant Secured. Server Exposed?
Finishing the cloud-email deployment doesn't finish incident response for the customer's servers.

Scheduled on LinkedIn
More Evidence. Slower Audit.
Sending more files can make an audit request harder to resolve.

Scheduled on LinkedIn
Temporary Risk. Permanent Exposure.
A temporary security exception can outlive the person who approved it.

Scheduled on LinkedIn
Rebuilding the Same Evidence? Again?
The evidence your reviewer needs may already exist in your security tools.

Scheduled on LinkedIn
Resolved. No Record.
The repair may be right and the evidence may still be useless.

Scheduled on LinkedIn
Compliant Yesterday. Exposed Today.
A passing report can describe a security setting that no longer exists.
Corporate articles
Analog Informatics Corporation

Published on LinkedIn
Evidence Exists. Where Is It?
Evidence that exists but can't be found still stops the review. A training record in one system, access history in another, and a control result in somebody's inbox leave the team doing detective work.

Published on LinkedIn
Rotate a Password. Break Production.
A password rotation can succeed while an application fails. The account has its new credential; a dependent service is still trying the old one.

Published on LinkedIn
Run Cybersecurity Like a Good Machine Shop
Make CMMC practical with the same tools, process, training, and routine checks that keep a machine shop productive, with evidence captured as work happens.

Published on LinkedIn
Your Audit Is Eating Engineering
The assessment invoice doesn't include the engineers pulled away from production to hunt for evidence. That time comes out of maintenance, delivery, and improvements the business needed.

Published on LinkedIn
One Password. Everyone’s Admin.
An ‘Administrator’ entry in a log may tell you nothing about who was at the keyboard. If the whole team knows the password, so can someone who shouldn't have it.

Published on LinkedIn
Should You Use a SaaS Email/VDI Solution for CMMC or Host It Yourself?
Deciding between hosted CUI email, cloud VDI and a customer-operated enclave? See where each approach fits and what to ask before choosing.

Published on LinkedIn
Overcoming CMMC Chaos, Failure, and Fines
Move from disconnected tools and manual evidence to standardized CMMC deployment kits, integrated security tools, and repeatable operations.

Published on LinkedIn
How an AIC OT Enclave Could Block a Danfoss Style Compromise
Keeping vulnerable industrial equipment running behind a tightly controlled boundary is an established approach.

Scheduled on LinkedIn
Employee Gone. Access Remains.
The employee left. The access didn't. Disabling one identity is only the beginning if other privileged access paths remain.

Scheduled on LinkedIn
Trained on the Wrong Policy?
A training completion record can be perfectly accurate and still answer the wrong question. Which version of the policy did that person actually acknowledge?

Scheduled on LinkedIn
Fixed? Prove It.
A repair command returned success. The security setting is still wrong. Close the ticket now and the next person inherits a problem marked FIXED.

Scheduled on LinkedIn
Bought the Kit. Who Runs It?
Buying a CMMC software kit doesn't fill in the operating roster. Somebody still has to own configuration, access decisions, training follow-up, and review of the evidence.

Scheduled on LinkedIn
Tenant Secured. Server Exposed?
A well-protected tenant can still sit beside a poorly controlled server. Identity controls at one layer don't explain every privileged session or configuration change elsewhere.

Scheduled on LinkedIn
More Evidence. Slower Audit.
More screenshots can mean a slower audit. If the reviewer can't connect them to the request, system, and time period, somebody still has to explain the pile.

Scheduled on LinkedIn
Temporary Risk. Permanent Exposure.
A temporary security exception shouldn't outlive the person who approved it. Yet a workaround can become part of the architecture simply because nobody revisits it.

Scheduled on LinkedIn
Rebuilding the Same Evidence? Again?
The same access event shouldn't require three separate investigations because three reviewers want different evidence formats.

Scheduled on LinkedIn
Resolved. No Record.
‘Resolved’ is a lousy handoff when nobody can tell what changed. The customer has a closed ticket. The MSP has moved on. Now an assessor wants the record.

Scheduled on LinkedIn
Compliant Yesterday. Exposed Today.
A clean assessment snapshot can't tell you what changed the following week. A new privileged account, a configuration exception, or an overdue review can change the picture quickly.

Scheduled on LinkedIn
Why CMMC was paused, and what actually fixes it
CMMC certification was paused because it was too expensive, too slow, too chaotic, and too manual. The fix is a standardized, integrated way to deploy.

Scheduled on LinkedIn
Your SPRS score is a sworn statement
How the NIST SP 800-171 SPRS score is calculated, why a senior official's affirmation carries False Claims Act risk, and how to keep the score matched.











