Most “platform security” problems aren’t zero-days. They’re:.•Too much access.•Missing patches.•No audit logs.•Secrets in plain text. Secure the boring stuff first. That’s what gets exploited.

RT @Franc0Fernand0: As a senior software engineer, you should read these famous white papers from big tech companies (AWS, Google, Meta,. )….

RT @lmoroney: Exciting news! My new book, AI and ML for Coders in PyTorch has finally arrived! I'm deeply grateful to my friend and mentor….

No logs, no visibility. No visibility… .No security.

RT @DanKornas: Machine Learning for Hackers

Top 5 Platform Security Mistakes (learned from real breaches):.1. Secrets in logs (Uber 2016).2.Overbroad IAM roles (Capital One).pipelines = soft targets (Codecov).insider threat model (Twitter 2020).5.Patching only when.

RT @mischa_vdburg: Security is everyone's job. Shift left. Secure by default.

RT @7h3h4ckv157: Meme of the day! 💯

Another presentation piece of advice ! . Adding quizzes to your presentations will drives engagement…. Especially if you promise chocolate for the winners ! 😃. Even if your product (pipeline, automation etc. ) .You still need to sell it !.

RT @yourclouddude: Don’t overthink it. • Build a Calculator to master logic & loops.• Build a Weather App using live APIs.• Build a CRUD We….

A piece of advise for presentations. Don’t forget to mix slides and interactive diagrams! . This will make your presentation better. Why ? . Think about the different type of learners. Auditory, Visual, Verbal, Logical….

The best security interview question ? . “How would you secure a 3-tier app in the cloud? Walk through your approach across network, identity, data, and workloads - from prevention to detection and response.”.

EKS Access Entries vs aws-auth ConfigMap – Access Control Cheat Sheet ! . - Access Entries = AWS-native method to grant EKS cluster access.- aws-auth ConfigMap = In-cluster YAML mapping IAM roles/users to RBAC

Most breaches start with one thing: lingering access. An ex-employee still in 3 SaaS apps?.A contractor never deprovisioned?.That’s your blast radius expanding. SCIM is how you shrink it. Real-time user sync. One source of truth. Security hygiene that actually scales.

SCIM isn’t just about automation. It’s about eliminating identity drift. Manual provisioning = human error.Stale accounts = privilege creep.Missed revocations = breach waiting to happen. SCIM fixes that. Least privilege at scale. Security teams who get it, use it.

SCIM is the protocol that quietly scales your identity management. No more manual user creation. No more “who forgot to remove Bob?”.No more chaos when teams grow fast. Set up once. Sync everywhere. Provision. Deprovision. Done. Most secure teams?.Already using it.

Lesson learnt number 1 . Raspberry Pi 5 gets really hot. so buy a box and the active cooling system 🤣

@goteleport.

Want VPN-less, auditable, Zero Trust access to internal apps?. "tsh proxy app" launches a local TLS proxy with your cert and tunnels traffic via ALPN + mTLS. ✔️ AuthN via short-lived certs.✔️ App-level routing.✔️ Full audit logging.✔️ Zero VPN surface. It’s PAM meeting ZTA. 🔐.

Words matter. Especially when you want to move up. Using the right terms = clear thinking + leadership trust. Share this with someone who keeps saying “we shipped it” when they just pushed code 😅. Follow me for more tech clarity 👇.