<story><title>How Not to Acknowledge a Data Breach</title><url>https://krebsonsecurity.com/2019/04/how-not-to-acknowledge-a-data-breach/</url></story><parent_chain><item><author>lainga</author><text>Who uses outsourcing firms like Wipro (government agencies)? What do they &lt;i&gt;do&lt;/i&gt;? It seems to me, living in the bubble of &lt;i&gt;haute tech&lt;/i&gt;, that the only things you ever hear about these firms are (a.) they exist and (b.) they are very large.</text></item></parent_chain><comment><author>korethr</author><text>One of the things they do is man the call centers in which the call agents are only allowed to: a) open tickets b) follow a script intended for people who didn&amp;#x27;t do basic troubleshooting before calling tech support c) be very sorry that your business is losing money due to the service interruption d) give you vague non-answers as to when the team with the authority to actually fix things but which is not allowed to interact directly with customers will actually get around to working on your issue, and e) ask you to kindly rate them highly on the customer satisfaction survey that you will be automatically connected to after this call.&lt;p&gt;Another thing they do is supply you with an endless cascade of developers who rotate in and out of your dev team on a 3-month basis. In those three months they will a) tell your IT team that they need a newer laptop because their current one gets slow when trying to run 3 instances of Visual Studio concurrently b) wonder why hard drive failures are correlated with rough handling of the laptop c) ask IT to troubleshoot their compilation errors d) only save their code locally instead of to a shared repo e) get upset when 3 months of said locally saved code, which IT was never told about, gets lost when the laptop, previously issued to the dev they replaced, is re-imaged before redeployment as per company policy&amp;#x2F;standard-procedure f) thereafter dodge turning in laptops to IT after their rotation ends, instead giving it directly to their replacement, causing IT&amp;#x27;s stores of deployable laptops to get depleted, and thus causing IT to come hunting after the never-turned-in laptops, because the next wave of 3-month devs is coming and hardware to issue them is needed, and finally g) treat company-issued laptops so roughly that when IT eventually does them back, what was brand shiny and new 3 months prior is now chipped, cracked, scratched and covered in grease and crumbs, and has a full kitten&amp;#x27;s worth of fluff accumulation in the cooling fan.&lt;p&gt;Okay, that last one was a bit hyperbolic, but every single point there did happen, and more than once.&lt;p&gt;Yes, I have been embittered by contractors from these large Indian IT firms, both as an end user &amp;#x27;supported&amp;#x27; by them and as a co-worker supporting them. My experience with them has not been a positive one.</text></comment>
<story><title>How Not to Acknowledge a Data Breach</title><url>https://krebsonsecurity.com/2019/04/how-not-to-acknowledge-a-data-breach/</url></story><parent_chain><item><author>lainga</author><text>Who uses outsourcing firms like Wipro (government agencies)? What do they &lt;i&gt;do&lt;/i&gt;? It seems to me, living in the bubble of &lt;i&gt;haute tech&lt;/i&gt;, that the only things you ever hear about these firms are (a.) they exist and (b.) they are very large.</text></item></parent_chain><comment><author>__david__</author><text>A company I worked at bought Firewire driver code from them (this was 15-20 years ago). The code was really, really terrible and we eventually had to replace it with our own code (which was 20x shorter, faster, and more spec compliant).&lt;p&gt;In retrospect, and as much as we in engineering hated their code, it was probably worth what they paid for it just because it got us 75% there and took pressure off the team while we created the replacement code.</text></comment>