|
|
|
| Authored by: PolR on Tuesday, July 17 2012 @ 09:07 PM EDT |
A coding mistake alone does not suffice to explain this situation.
Where was to compliance auditor? Did anyone in Microsoft legal or internal audit
department insist to check that Microsoft remains in compliance at all time? The
auditor should have caught the coding mistake well before the software is out of
the door. Or failing that he/she should have caught the mistake immediately
after release. This fall back scenario is still incompetent but much better than
what happened.
On top of the coding mistake, if this was the mistake, there must have been a
failure to properly audit for compliance.
At the very least, Microsoft was not serious enough about compliance. They
didn't do what needed to be done to be in compliance.
[ Reply to This | Parent | # ]
|
| |
| Authored by: Anonymous on Tuesday, July 17 2012 @ 09:57 PM EDT |
Is something that Microsoft does not do;- at all.
No matter what the verdict Microsoft will still deny doing anything morally or
legally wrong.
Or so I seem to observed.
Chris B
[ Reply to This | Parent | # ]
|
|
|
|
|
