Timeline for What are some sensible approaches for dealing with 4,000 vulnerabilities across 700 databases in 70 servers
Current License: CC BY-SA 4.0
3 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Oct 11, 2023 at 15:01 | comment | added | J.D. | @Potatan For sure, np. I can't imagine that they're using 70 different vendors for supplying their software as well. All software from the same vendor should share the same server instance (without a good reason otherwise specific to that app). And perhaps it's even reasonable to use the same server instance to host databases for software between different vendors. Just depends on the vendor and software. | |
| Oct 11, 2023 at 13:53 | comment | added | Potatan | Thanks, some useful suggestions there. One issue is that a lot of the databases are vendor-supplied so use the vendor's own ideas about what constitutes reasonable "security". However, removing of legacy databases/servers and combining others may have some mileage in it as an initial way of approaching the problem. | |
| Oct 9, 2023 at 14:59 | history | answered | J.D. | CC BY-SA 4.0 |