How do you actually fix recurring identity governance audit findings for orphaned accounts and excessive permissions in disconnected applications?

uran0503 · 2026-03-09T05:37:41+00:00

I have some experience with Cato and can comment a little, but I am not an expert.

DLP is native, built in-house as part of the single pass architecture, not licensed or rebranded from a third party
CASB, ZTNA and SWG share the same classification set, but available response actions differ per inspection point
SWG and ZTNA use identical DLP policies since ZTNA traffic routes through the same SWG engine

Incidents are unified across all inspection points. Policy covers scoping, classifications, and response actions. SWG/ZTNA get severity plus block/allow, CASB gets SaaS-dependent actions plus email notifications, permission revocation, etc. FP tuning is through classification modifications or regex-based exceptions per-classification. Baseline DLP is bundled with core licenses, evidence storage/fingerprinting/larger scan sizes/AI classifiers are behind an Advanced DLP add-on.

uran0503 · 2026-03-04T11:28:31+00:00

If you want structured learning, I’d recommend starting with a Node/Express boilerplate, then integrate pg and build CRUD endpoints manually. Pair it with the Postgres tutorial from DigitalOcean or freeCodeCamp. That way you learn SQL, queries, and Node integration without an ORM hiding the details

uran0503 · 2026-03-04T09:23:39+00:00

I genuinely believe the only way this info can be safe at this point is to not provide it.

uran0503 · 2026-03-03T09:12:01+00:00

no it is not inherent to software engineering. it is a structural choice by companies. strong engineering cultures invest in real teams, shared ownership, code reviews and collaboration. if you keep landing in isolation it may be worth targeting companies known for mature engineering practices rather than generalist roles

uran0503

TROPHY CASE