Dev.to Security ๐Ÿ” Cybersecurity ๐Ÿ‘ 0 ๐Ÿ“– 2 min read

An Auditor Wants to Ask You How Code Reaches Production

Your company is working towards a security certification, and the auditors are in this week. Your manager tells you that one of them wants to talk to an engineer about how changes reach production. They have picked you.

Your company is working towards a security certification, and the auditors are in this week. Your manager tells you that one of them wants to talk to an engineer about how changes reach production. They have picked you. The meeting is forty five minutes, tomorrow morning, and your stomach drops a little.

It helps to understand what the auditor is doing. They are not testing you, and they are not trying to catch you out. They are checking whether the company does what its written policies say it does. The policy might say every change is reviewed by a second person and deployed through a pipeline. The auditor wants to hear how that actually happens, from someone who does it, and then see evidence that it happened.

So prepare by reading the policy, not by memorising answers. Ask your manager or the person running the audit for the relevant documents, and read the parts about code review, testing, deployment and access. Then walk through a recent change of your own, from ticket to pull request to approval to release, and check that you can point to each step.

In the meeting, answer the question you were asked, and then stop. Auditors often ask short, open questions. How do you know a change was approved? Who can deploy to production? A clear answer with an example is better than a long tour of every exception you can think of.

If you do not know something, say so. I am not sure how that works, but I can find out, or the platform team will know, is a perfectly good answer. A confident guess is much worse, because it may not match the evidence, and then a small gap turns into a finding.

If you do know of a gap, do not hide it. Perhaps there is an emergency process that skips review. Describe it honestly, along with how it is recorded. Most audits expect some exceptions. What matters is that they are known and controlled.

Afterwards, tell your manager anything that surprised you. You have probably just learned more about how your company manages risk than most of your team.

โ€“ Asael Shinder

๐Ÿ“ฐ Read the original article on Dev.to Security

Originally published by Dev.to Security. Aggregated on AIWithGhost for educational purposes โ€” full credit and traffic to the original publisher.