Yesterday, cyber resilience startup, UpGuard, issued a report that as many as 14 million U.S. Verizon customers have fallen victim to a hack that stole their names, addresses, account details, and PINs. The startup claims to have first notified Verizon on June 13th of the hack, citing a "misconfigured cloud-based file repository" as the cause.
In reply, Verizon has stated that there has been no loss or theft of customer information and that only 6 million customers may be at risk due to an informational cloud storage move where a third-party employee made external access available. Latest reports urge Verizon customers to update their Verizon PINs in order to safeguard their accounts.
Stay tuned for more information on what happened in this attack and how to safeguard your accounts.
We are using Informatica 10.2 R1 for extract, masking, subset using Informatica's Test Data Manager. We have a large volume of DB2 tables to mask and subset from production on an Iseries and mainframe. The problems we are having are designing entities so that they are small enough to manage. However, not all parent tables are represented for the child tables especially when we run into circular relationships. Can one entity be large enough to accommodate all 720 tables?