Programming

423 readers

4 users here now

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Follow the programming.dev instance rules
Keep content related to programming in some way
If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities !webdev@programming.dev

founded 1 year ago

MODERATORS

snowe@programming.dev

Ategon@programming.dev

MaungaHikoi@lemmy.nz

How to conduct a software audit? (lemmy.pe1uca.dev)

submitted 6 months ago by pe1uca@lemmy.pe1uca.dev to c/programming@programming.dev

6 comments fedilink hide all child comments

I need to help auditing a project from another team.
I got the pointers on what's expected to be checked, but I don't have like templates for documents for what's expected from an audit report which also means I'm not sure what's the usual process to conduct an internal audit.
I mean I might as well read the whole repo, but maybe that's too much?

Any help or pointers on what I need to investigate to get started would be great!

top 6 comments

sorted by: hot top controversial new old

[–] folkrav@lemmy.ca 19 points 6 months ago (1 children)

I won’t lie, I’m a bit curious why someone asked someone who has never performed an audit to perform one, what they’re actually hoping to find, and what they plan on doing with the results…

[–] coloredgrayscale@programming.dev 7 points 6 months ago (1 children)

Maybe they see OP as the best candidate for an audit or code review, who has good enough skills, has time available, and is an internal resource

[–] folkrav@lemmy.ca 5 points 6 months ago

I’m just having trouble calling that an “audit”.

[–] Cratermaker@discuss.tchncs.de 3 points 6 months ago

Maybe the word "audit" is incorrect? If they didn't provide you any guidelines, I'd definitely recommend asking. But it's possible they're just looking for your perspective on best practices and possible improvement ideas, more like a general code review.

[–] Kissaki@programming.dev 1 points 6 months ago

Ironic that you don't share the pointers on what's expected to be checked with us.