News for hackers. Stuff that matters.
Re:20GB leak of Intel data: whole Git repositories, dev tool... by Sylamore on Thursday August 06, 2020 @11:28PM (#24077804)
One thing I learned when I worked in internal IT security when dealing with auditors was that they will boil the ocean to find an issue, so never be perfect and leave a few relatively easy but not obvious to spot issues for them to write up that don't actually affect the security of your environment. If you don't leave them this bait, they will spend weeks to find a trivial issue (like using MD5 to check for config file changes vs password hashing) and turn it into a massive issue they won't budge on.

The other issue is that if you make it seem too easy to answer their questions or provide reports, they will only ask more questions or demand more reports so even if its just dumping a list of users into a CSV file for them to review, make it seem like way more effort than it actually is otherwise you might find you've been forced into a massive amount of busy work while they continue to boil the ocean.

Re:20GB leak of Intel data: whole Git repositories, dev tool... by blablablub on Friday August 07, 2020 @05:51AM (#24080192)
Smart auditors ask for all items at the beginning of the audit. Smart IT people give them all items at the end of the audit. Auditors have only a limited time budget. The later they get answers, the less time for them is left for follow-up questions.
Re:20GB leak of Intel data: whole Git repositories, dev tool... by data_ders on Friday August 07, 2020 @02:50AM (#24079079)
3D chess! I agree sometimes it feels as if the security review questions are just set-ups for follow-ups that they didn’t include in the initial form (for whatever reason)