Ask Lemmy
A Fediverse community for open-ended, thought provoking questions
Rules: (interactive)
1) Be nice and; have fun
Doxxing, trolling, sealioning, racism, and toxicity are not welcomed in AskLemmy. Remember what your mother said: if you can't say something nice, don't say anything at all. In addition, the site-wide Lemmy.world terms of service also apply here. Please familiarize yourself with them
2) All posts must end with a '?'
This is sort of like Jeopardy. Please phrase all post titles in the form of a proper question ending with ?
3) No spam
Please do not flood the community with nonsense. Actual suspected spammers will be banned on site. No astroturfing.
4) NSFW is okay, within reason
Just remember to tag posts with either a content warning or a [NSFW] tag. Overtly sexual posts are not allowed, please direct them to either [email protected] or [email protected].
NSFW comments should be restricted to posts tagged [NSFW].
5) This is not a support community.
It is not a place for 'how do I?', type questions.
If you have any questions regarding the site itself or would like to report a community, please direct them to Lemmy.world Support or email [email protected]. For other questions check our partnered communities list, or use the search function.
Reminder: The terms of service apply here too.
Partnered Communities:
Logo design credit goes to: tubbadu
view the rest of the comments
One IT security team insisted we have separate source code repositories for production and development environments.
I’m honestly not sure how they thought that would work.
That's fucking bananas.
In my job, the only difference between prod/dev is a single environmental file. Two repositories would literally serve no purpose and if anything, double the chances of having the source code be stolen.
That was the only difference for us as well. The CI/CD process built container images. Only difference between dev, test, and prod was the environment variables passed to the container.
At first I asked the clueless security analyst to explain how that improves security, which he couldn’t. Then I asked him how testing against one repository and deploying from another wouldn’t invalidate the results of the testing done by the QA team, but he kept insisting we needed it to check some box. I asked about the source of the policy and still no explanation, at least not one that made any sense.
Security analyst escalated it to his (thankfully not clueless) boss who promptly gave our process a pass and pointed out to Mr security analyst that literally nobody does that.
Just manually copy-paste everything. That never goes wrong, right?
I mean, it's what the Security guys do, right? Just copy+paste everything, mandate that everyone else does it too, Management won't argue because it's for "security" reasons.
Then the Security guys will sit around jerking each other off about how much more secure they made the system
Could work if dev was upstream from prod. But honestly there would be no difference between that and branches.
Maybe it is a rights issue. Preventing a prod build agent of sorts to access develop code.
Yeah....assuming that the policy was written "from blood" (meaning someone did something stupid).
But even then you can put other checks and balances in place to make sure that kind of thing doesn't happen.
This is such an extreme reaction though. Or the policy was made from someone dumb
Yep doing that now. Not sustainable in the slightest. Im glad im not in charge of that system.