3 ms·
Pretty sure the various organizations within the enterprise had an individual responsible for their domain. At worst, it's a bit bucket search within ones org/d
by giantg2 5y ago
Pretty sure the various organizations within the enterprise had an individual responsible for their domain. At worst, it's a bit bucket search within ones org/domain for the library. The testing is the more complicated part.
It's not an easy situation either way, but the identification portion should be trivial.
- ygjb 5y agoDepends on how the organization grew, and if they have unified processes across department. AFAIK the IT security folks at a financial institution that I used to work at are living in hell at the moment. That organization grew internationally through acquisitions across more than 80 countries, and lacks unified structure across the entire organization due to legal and compliance constraints unique to each jurisdiction. A web development shop I provide security guidance to (owned by one my TTRPG buddies) had to do a couple of searches in github and update some hardware as patches became available. We made sure he was sorted out over a couple of drinks before we played board games. It varies.
- giantg2 5y agoThat does sound like a nightmare.
- greedo 5y agoSure. We have a codebase and app stack that has grown over 40 years. Responsible Parties have come and gone, sometimes handing off ownership responsibly, but often there wasn't enough time. So someone may be "responsible" for application X, but they haven't looked at the code in any detail. Or application X was installed by a vendor who provided documentation back in 2002 that is long gone. Nothing is trivial in large organizations.
- giantg2 5y agoI mean, we could say nothing is ever trivial, period.