Originally Posted by
phltraveler
As I made post
#48 , I don't think that it's
useless finger pointing to point out that the breach started under Starwood but Starwood's liabilities are Marriott's, and express disbelief that a system that Marriott had been working on integrating with their own website/rewards IT for over two years remained compromised throughout the entire integration period, including after the Single loyalty program/website integration on 08/18, and that the security breach was only found after they had integrated the starwood reservation system/servers with Marriott.com and Marriott Rewards. Given that it's another failure on the part of the combined Marriott/Starwood from an IT perspective, groaning is going to come with the territory.
.
Granted, your post contained little finger pointing and additional information, but so many others are like this:
Originally Posted by
tfong007
How does the CTO still have a job. This is a case study of how not to handle a merger. What a total cockup. Seems like every day things get worse. Not better
and this:
Originally Posted by
X-ON
Wow what a fiasco of a merger... It is really not that interesting if we attribute this to SPG Mickey Mouse security protocols or a subpar due diligence by Marriott the end result is a fiasco merger at best or catastrophic merger at worst. Mr Sorenson should thank his lucky star if he survives this.
and this:
Originally Posted by
oxfordjames
Have you even read the cause of this breach? This was an SPG issue!!
Last edited by CJKatl; Nov 30, 2018 at 8:58 am