MarcMenninger Profile Banner
Marc Menninger Profile
Marc Menninger

@MarcMenninger

Followers
5K
Following
80K
Media
178
Statuses
7K

Helping you escape your crappy job & transition into an exciting cybersecurity career in only 2 hrs/day | LinkedIn Learning instructor | Career coach

Take the course:
Joined December 2010
Don't wanna be here? Send us removal request.
@MarcMenninger
Marc Menninger
4 months
1
0
6
@MarcMenninger
Marc Menninger
4 months
7️⃣ Final Takeaway 🔑. Access reviews reduce risk, boost compliance, and force teams to think critically about who has access to what and why. ✔️ Start small. ✔️ Focus on impact. ✔️ Make it a habit. 📌 Bookmark this thread if you’re building your review process or prepping for.
0
0
3
@MarcMenninger
Marc Menninger
4 months
6️⃣ How to Make It Happen (With Minimal Hassle). ✅ Pull reports from your IAM or HR system. ✅ Highlight high-risk users first (admin, elevated, contractors). ✅ Pre-fill recommendations: Keep, Remove, Review. ✅ Set a due date and follow up. Add a dashboard if you want to be.
1
0
2
@MarcMenninger
Marc Menninger
4 months
5️⃣ When to Do It?. 📅 Quarterly is the sweet spot for most orgs. 🔹 Too frequent = ignored. 🔹 Too rare = stale access. 🔹 Align with role changes, onboarding/offboarding cycles, and audits. Consistency > perfection.
1
0
0
@MarcMenninger
Marc Menninger
4 months
4️⃣ Who Should Do It?. Not IT. Not Security. Not alone, anyway. The right people are:. 🔹 System Owners – they know who needs what. 🔹 Managers – they know team responsibilities. 🔹 Security/GRC – to guide and track the process. Ownership matters more than automation.
1
0
0
@MarcMenninger
Marc Menninger
4 months
3️⃣ What to Review (Start Here). 🔍 Focus on high-impact areas:. 🔸 Admin access. 🔸 Finance + HR systems. 🔸 Production environments. 🔸 Identity + access management tools. Start small. Expand from there.
1
0
0
@MarcMenninger
Marc Menninger
4 months
2️⃣ What’s the Point?. Access reviews aren’t busywork. Done right, they help you:. ✅ Enforce least privilege. ✅ Spot orphaned or risky accounts. ✅ Clean up over-permissioned users. ✅ Prepare for audits (ISO 27001, SOC 2, etc.). They're one of the simplest ways to prove.
1
0
0
@MarcMenninger
Marc Menninger
4 months
1️⃣ Why Access Reviews Matter. 🔹 People switch roles. 🔹 Contractors overstay. 🔹 Former employees slip through the cracks. 🔹 Privileged access stacks up quietly. Every unused or unnecessary permission = a liability.
1
0
2
@MarcMenninger
Marc Menninger
4 months
🧾 Access Reviews: Why They Matter and How to Get Them Done. Most orgs say they do access reviews. Few do them well. Fewer do them consistently. If you want to reduce risk, pass audits, and avoid awkward breaches, this thread is for you. 🧵.
3
4
31
@MarcMenninger
Marc Menninger
4 months
🔑 Final Takeaway: Access control is one of the highest-impact areas you can clean up - if you take it seriously. ✔️ Least privilege. ✔️ Timely reviews. ✔️ No shared accounts. ✔️ Scoped, contextual, accountable access. 📌 Bookmark this thread to tighten your access strategy.
0
0
4
@MarcMenninger
Marc Menninger
4 months
7️⃣ No Ownership or Accountability. Who owns access reviews for Salesforce? For GitHub? For that legacy database?. If it’s “nobody” or “just IT,” that’s a problem. ✅ Fix it: Assign business owners to key systems. They know who should have access - and who shouldn’t.
1
0
1
@MarcMenninger
Marc Menninger
4 months
6️⃣ No Context-Based Controls. If anyone can log in from anywhere, anytime, with full access, that’s a red flag. ✅ Fix it:. 🔹 Use Conditional Access or risk-based policies. 🔹 Require step-up auth for sensitive actions. 🔹 Restrict by device, location, or risk level. Security.
1
0
0
@MarcMenninger
Marc Menninger
4 months
5️⃣ Ignoring Non-Human Access. Service accounts. API keys. Automation tokens. They often:. 🔹 Have broad privileges. 🔹 Never expire. 🔹 Are hardcoded or forgotten. ✅ Fix it: Treat non-human identities like users. Scope tightly. Rotate often. Monitor usage.
1
0
1
@MarcMenninger
Marc Menninger
4 months
4️⃣ Weak or Unenforced Offboarding. The moment someone leaves, their access should end. Not “eventually.” Not “when HR tells us.”. ✅ Fix it:. 🔹 Automate terminations. 🔹 Include vendors + interns. 🔹 Audit access logs for ghost users. Offboarding delays = free access for.
1
0
2
@MarcMenninger
Marc Menninger
4 months
3️⃣ Shared Accounts Are Still a Thing. Yes, some orgs still use:. 🔹 "admin/admin123". 🔹 Shared logins for firewalls or servers. 🔹 One AWS or Azure account for the whole team. ✅ Fix it: Use named accounts, enforce MFA, and kill shared creds. No accountability = no visibility.
1
0
2
@MarcMenninger
Marc Menninger
4 months
2️⃣ No Regular Access Reviews. Access granted = access forever? That’s how breaches happen. If no one’s checking:. 🔹 Who has access. 🔹 Whether they still need it. 🔹 When it was last used. Then you’re flying blind. ✅ Fix it: Run quarterly reviews. Focus on high-risk.
1
0
5
@MarcMenninger
Marc Menninger
4 months
1️⃣ Too Much Access, Too Fast. 🔹 New hires get added to broad roles “just to get started”. 🔹 Contractors get admin because “it’s easier”. 🔹 Access requests are rubber-stamped. ✅ Fix it: Start with least privilege, not full access. Make justifications mandatory and time-bound.
1
0
3
@MarcMenninger
Marc Menninger
4 months
🔐 The 7 Most Common Access Control Mistakes (And How to Avoid Them). Access control isn’t glamorous, but it’s one of the biggest sources of risk in every organization. Here are the mistakes I see most - and how you can fix them before they lead to a breach. 🧵.
1
10
72
@MarcMenninger
Marc Menninger
4 months
🔑 Final Takeaway: Security architects are the glue between security, engineering, and business. ✔️ You translate strategy into structure.✔️ You prevent problems instead of reacting to them.✔️ You make security scalable. 📌 Bookmark this thread if you’re thinking about growing.
1
0
5
@MarcMenninger
Marc Menninger
4 months
6️⃣ Navigate tradeoffs. Security vs. speed. Compliance vs. usability. Budget vs. control. Security architects make the tough calls - or guide the people who do. You need technical depth + business sense + communication skills.
1
0
2
@MarcMenninger
Marc Menninger
4 months
5️⃣ Lead threat modeling sessions. Not every day - but often enough. Sit down with devs, product managers, and engineers to map out: . 🔹 What could go wrong.🔹 Where the biggest risks are.🔹 How to build in controls early. It’s part education, part design review, part mental.
1
0
1