Re:Equifax securities fraud class action [pdf]
by bouncycastle on Tuesday October 22, 2019 @08:30AM
(#21322836)
Colleague #3: "Sounds good to me. We're behind the firewall and the NIC used for Dell iDRAC or HP iLO is on an isolated network unique to the physical datacenter. Remote access for our techs is managed through a secured bridge that requires all sorts of security hoops on our company intranet, and remote access for general internet traffic is not available due to the firewall restrictions. There's no way hackers will get through that in the first place."
[ Parent
| on HN ]
Re:Equifax securities fraud class action [pdf]
by Legogris on Tuesday October 22, 2019 @08:40AM
(#21322900)
Colleague #4-20: Build various integrations to database, all with their own ways of storing credentials.
Colleague #2: "It's really past due time to change the database password, but first we have to make sure all critical systems can still access the database."
Re:Equifax securities fraud class action [pdf]
by bloopernova on Tuesday October 22, 2019 @09:25AM
(#21323316)
Which is why forward planning and prompt action is worth so much.
I know I'm stating the obvious, but I've seen some worrying attitudes of "just in time" that seem to go hand in hand with a misunderstanding of Scrum Sprints or Kanban. Where people concentrate on the tree and ignore the vast interconnected forest around them.
Re:Equifax securities fraud class action [pdf]
by dspillett on Tuesday October 22, 2019 @09:57AM
(#21323617)
Hence the old adage: days of work can save you hours of planning.
Re:Equifax securities fraud class action [pdf]
by elisharobinson on Tuesday October 22, 2019 @10:39AM
(#21324097)
manager: why is it taking so long to deploy a simple cluster. back in my day we could code a whole ...
Re:Equifax securities fraud class action [pdf]
by peterkelly on Tuesday October 22, 2019 @09:32AM
(#21323386)