Feed
Pro
Search

Author

Write
Drafts

Bug0 - The AI-native e2e QA regression testing Passmark - The open-source AI framework for regression testing Hackathons Changelog Brand Hashnode gql skill - let your AI agent publish to your Hashnode blog The Foreword by Hashnode - official blog from the Hashnode team @hashnode on X Hashnode on LinkedIn Support - hello+support@hashnode.com Code of Conduct Terms Privacy Sitemap
Sign in

Search Hashnode

Search posts, tags, users, and pages

Discussion on "Security Assessments: Evaluating Security Across People, Process, and Technology" | Hashnode

FeedDiscussion

Manuela Schrittwieser

Full-Stack AI Dev 👩🏻‍💻 & Tech Writer

Apr 27

Security Assessments: Evaluating Security Across People, Process, and Technology

NeuralStack | MS — Article 2 of 3 Part 2 of the AI Security & Cybersecurity Series If penetration testing is a scalpel – precise, targeted, adversarial – then a comprehensive security assessment is t

neuralstackms.tech9 min read

#aisecurity #securityassessment #cybersecurityframeworks #securityprogrammanagement #risk-management #information-security #securityaudit

Responses(3)

Suny Choudhary

Good framing. Security assessments only work when they look beyond tooling. A company can have strong products in place and still fail because access reviews are weak, processes are unclear, or people don’t know what “secure behavior” looks like in daily work. The people, process, technology split is still one of the most practical ways to find real gaps.

Building AI Security for LLMs | CEO @ LangProtect

Apr 29

Manuela Schrittwieser

Full-Stack AI Dev 👩🏻‍💻 & Tech Writer

Apr 29

Precisely. The PPT (People, Process, Technology) framework remains the industry standard because it addresses the systemic dependencies that technical controls alone cannot solve. A secure-by-design infrastructure is often undermined by insecure-by-habit workflows.

Suny Choudhary

Building AI Security for LLMs | CEO @ LangProtect

Apr 29

That’s exactly where most programs break. Even when infra is secure by design, the actual risk shows up in everyday workflows. People bypass steps, share data differently, or use tools in ways policies never accounted for.

Feels like the gap now is less about defining controls and more about seeing how they behave in real usage.