
What Does a Security Engineer Actually Do All Day?
transcript
show notes
It is a quarter past eight on a Tuesday morning, and the first message of the day is already a problem: a business team needs an outside vendor to reach two internal servers by Thursday. In this episode I follow one hypothetical security engineer through a single workday to show what the job actually involves.
You will see the engineer write the requirement before touching any tools, connect the vendor through existing remote access with narrow firewall rules, troubleshoot a security agent policy that broke a finance application, make a narrow and documented exception, run a small pilot with a rollback ready, send the right logs to the central logging platform, and verify that the access works and that everything else stays blocked. I finish with a short four-line assignment you can do with a control you already manage or have built in a lab.
It is for system administrators and network administrators who wonder whether security engineering is out of reach. The company, the vendor and every detail are made up for teaching, and no products are named. This is education, not legal or technical advice for your environment.
Summary: One hypothetical security engineer's workday: requirement-first design, vendor access, troubleshooting a security agent policy, a narrow documented exception, pilot and rollback, logging, and verification, plus a short four-line assignment.
Show notes:
- What a security engineer actually does all day, shown through one hypothetical workday with a vendor access request.
- Why the first step is writing down what the access must allow and what it must block, before any design work.
- A narrower design: existing remote access service, multifactor authentication and firewall rules that reach only two servers on specific ports.
- Integration questions that separate engineering from drawing diagrams: where vendor accounts live and what turns them off when the contract ends.
- Troubleshooting something that worked yesterday: narrowing the problem, reproducing it on a test machine and confirming the cause before acting.
- Why a narrow, documented exception with an owner and a review date beats turning protection off or a broad exception.
- Staged rollout: a deliberately chosen five-machine pilot, a second narrow exception for a separate tool, and a written rollback.
- Logging for analysts: sending remote access and firewall logs to the central platform and checking that real events arrive with the details needed.
- Verification in both directions: the vendor can reach the two servers, and cannot reach anything else.
- The assignment: write four lines for one control (requirement, how you would test a change, how you would roll it back, one sentence of documentation) and find the line you could not fill in.
▶️ Companion YouTube Video: https://youtu.be/gnGmmwYZSOQ
📝 Companion Blog Post: https://professorsimon.com/blog/what-does-a-security-engineer-do-all-day
🎧 More Podcast Episodes: https://professorsimon.com/podcast
👉 Need help with your IT or cybersecurity career? Work with me: https://professorsimon.com/guidance
🎯 Cybersecurity Interview Prep Pack: https://professorsimon.com/products/cybersecurity-interview-prep-pack
🔗 Resources, blog & more: https://professorsimon.com/links
🌐 Website: https://professorsimon.com
💼 LinkedIn: https://www.linkedin.com/in/leonardsimon
📸 Instagram • X • TikTok: @profsimononline
- https://youtu.be/gnGmmwYZSOQyoutu.be
- https://professorsimon.com/blog/what-does-a-security-engineer-do-all-dayprofessorsimon.com
- https://professorsimon.com/podcastprofessorsimon.com
- https://professorsimon.com/guidanceprofessorsimon.com