2 ms·
Sigh. I don't have the docs in front of me, and even if I did, darned if I'm touching those diabolic tomes without a 10-foot pole and a paycheck. But they do sa
by kstrauser 3y ago
Sigh. I don't have the docs in front of me, and even if I did, darned if I'm touching those diabolic tomes without a 10-foot pole and a paycheck. But they do say something along the lines that all change requests have to have some kind of a ticket. The good/bad part is that it doesn't specify exactly what that means. If you can find an enlightened auditor who accepts an explanation in the PR, awesome! There's no guarantee that the _next_ auditor will see it the same way. The whole audit process was a back-and-forth with explaining why we think our controls satisfy the request, and the end result was a clean report.
> it isn’t SOC2’s fault, it is the fault of auditors who are afraid to not just do what everyone else does.
There's some liability for them if they're too lax. Suppose a breach happens and a given control, as written in the spec, would have prevented it. It could come back on the auditor who signed off on a clever interpretation of that control.
- jollyllama 3y agoI haven't worked on anything that had to adhere to that standard, but I also have yet to work somewhere where a "Change Request" was a very specific thing related to workflows that may or may not involve software, i.e. hardware. A pull request rarely had relation to a proper Change Request.
- kstrauser 3y agoA control that results in a paper trail without making anything materially better, but must still be obeyed to the letter because a certification depends on it? Why, I've never heard of such a thing, I do declare!