OT: Microsoft Office 365 Outlook (online variant) violates S

R

Robert Baer

Guest
Well, after downloading and installing Outlook 2019, i was able to
see the same e-mail folders with the same contents "on" my computer; i
doubt that is where that apparent copy resided; i think it was in the
"cloud".
Makes no diff; there i could File/Import Export/ etc to (chose CSV
ignored PST) to desktop.

NOW HERE IS THE NASTY:
Those CSV e-mail files are NOT SOX compliant!

Penalties for non-compliance: Formal penalties for non-compliance with
SOX can include fines, removal from listings on public stock exchanges
and invalidation of D&O insurance policies. Under the Act, CEOs and CFOs
who willfully submit an incorrect certification to a SOX compliance
audit can face fines of $5 million and up to 20 years in jail.

You ask what is wrong?
There is _NO_ date field, _NO_ time field and _NO_ headers field for
the e-mail entries, despite 19 other fields.
CSV fields are:
"Subject","Body","From: (Name)","From: (Address)","From: (Type)","To:
(Name)","To: (Address)","To: (Type)","CC: (Name)","CC: (Address)","CC:
(Type)","BCC: (Name)","BCC: (Address)","BCC: (Type)","Billing
Information","Categories","Importance","Mileage","Sensitivity"
 
On Fri, 27 Sep 2019 14:42:49 -0800, Robert Baer
<robertbaer@localnet.com> wrote:

Well, after downloading and installing Outlook 2019, i was able to
see the same e-mail folders with the same contents "on" my computer; i
doubt that is where that apparent copy resided; i think it was in the
"cloud".
Makes no diff; there i could File/Import Export/ etc to (chose CSV
ignored PST) to desktop.

NOW HERE IS THE NASTY:
Those CSV e-mail files are NOT SOX compliant!

Penalties for non-compliance: Formal penalties for non-compliance with
SOX can include fines, removal from listings on public stock exchanges
and invalidation of D&O insurance policies. Under the Act, CEOs and CFOs
who willfully submit an incorrect certification to a SOX compliance
audit can face fines of $5 million and up to 20 years in jail.

You ask what is wrong?
There is _NO_ date field, _NO_ time field and _NO_ headers field for
the e-mail entries, despite 19 other fields.
CSV fields are:
"Subject","Body","From: (Name)","From: (Address)","From: (Type)","To:
(Name)","To: (Address)","To: (Type)","CC: (Name)","CC: (Address)","CC:
(Type)","BCC: (Name)","BCC: (Address)","BCC: (Type)","Billing
Information","Categories","Importance","Mileage","Sensitivity"
Click to expand...

<https://www.microsoft.com/en-us/trustcenter/compliance/SOX>

Cheers
 
Martin Riddle wrote:
On Fri, 27 Sep 2019 14:42:49 -0800, Robert Baer
robertbaer@localnet.com> wrote:

Well, after downloading and installing Outlook 2019, i was able to
see the same e-mail folders with the same contents "on" my computer; i
doubt that is where that apparent copy resided; i think it was in the
"cloud".
Makes no diff; there i could File/Import Export/ etc to (chose CSV
ignored PST) to desktop.

NOW HERE IS THE NASTY:
Those CSV e-mail files are NOT SOX compliant!

Penalties for non-compliance: Formal penalties for non-compliance with
SOX can include fines, removal from listings on public stock exchanges
and invalidation of D&O insurance policies. Under the Act, CEOs and CFOs
who willfully submit an incorrect certification to a SOX compliance
audit can face fines of $5 million and up to 20 years in jail.

You ask what is wrong?
There is _NO_ date field, _NO_ time field and _NO_ headers field for
the e-mail entries, despite 19 other fields.
CSV fields are:
"Subject","Body","From: (Name)","From: (Address)","From: (Type)","To:
(Name)","To: (Address)","To: (Type)","CC: (Name)","CC: (Address)","CC:
(Type)","BCC: (Name)","BCC: (Address)","BCC: (Type)","Billing
Information","Categories","Importance","Mileage","Sensitivity"

https://www.microsoft.com/en-us/trustcenter/compliance/SOX

Cheers
Click to expand...
A lot of obfuscation yammer.
Note "there is no SOX certification or validation for cloud service
providers."
WE are trustworthy because we paid off Azure "more than US $300
billion annual cash movement."
Note they SAY nothing about data integrity: WHEN (day, time) was an
e-mail sent/received.
It is called trace-ability.
Critical.
 
Martin Riddle wrote:
On Fri, 27 Sep 2019 14:42:49 -0800, Robert Baer
robertbaer@localnet.com> wrote:

Well, after downloading and installing Outlook 2019, i was able to
see the same e-mail folders with the same contents "on" my computer; i
doubt that is where that apparent copy resided; i think it was in the
"cloud".
Makes no diff; there i could File/Import Export/ etc to (chose CSV
ignored PST) to desktop.

NOW HERE IS THE NASTY:
Those CSV e-mail files are NOT SOX compliant!

Penalties for non-compliance: Formal penalties for non-compliance with
SOX can include fines, removal from listings on public stock exchanges
and invalidation of D&O insurance policies. Under the Act, CEOs and CFOs
who willfully submit an incorrect certification to a SOX compliance
audit can face fines of $5 million and up to 20 years in jail.

You ask what is wrong?
There is _NO_ date field, _NO_ time field and _NO_ headers field for
the e-mail entries, despite 19 other fields.
CSV fields are:
"Subject","Body","From: (Name)","From: (Address)","From: (Type)","To:
(Name)","To: (Address)","To: (Type)","CC: (Name)","CC: (Address)","CC:
(Type)","BCC: (Name)","BCC: (Address)","BCC: (Type)","Billing
Information","Categories","Importance","Mileage","Sensitivity"

https://www.microsoft.com/en-us/trustcenter/compliance/SOX

Cheers
Click to expand...

Operational integrity of Office 365 is not mentioned anywhere, even
the IDEA of problems, bugs, etc NOT addressed in any manner.
ZERO discussion concerning export of data from Outlook, ZERO
discussion concerning ANY problems with Outlook.
In fact, it is rather hard to find ANY mention of Office 365 per se
except that it exists en passe.
 
Robert Baer wrote:
Martin Riddle wrote:
On Fri, 27 Sep 2019 14:42:49 -0800, Robert Baer
robertbaer@localnet.com> wrote:

   Well, after downloading and installing Outlook 2019, i was able to
see the same e-mail folders with the same contents "on" my computer; i
doubt that is where that apparent copy resided; i think it was in the
"cloud".
   Makes no diff; there i could File/Import Export/ etc to (chose CSV
ignored PST) to desktop.

   NOW HERE IS THE NASTY:
   Those CSV e-mail files are NOT SOX compliant!

Penalties for non-compliance: Formal penalties for non-compliance with
SOX can include fines, removal from listings on public stock exchanges
and invalidation of D&O insurance policies. Under the Act, CEOs and CFOs
who willfully submit an incorrect certification to a SOX compliance
audit can face fines of $5 million and up to 20 years in jail.

   You ask what is wrong?
   There is _NO_ date field, _NO_ time field and _NO_ headers field for
the e-mail entries, despite 19 other fields.
   CSV fields are:
"Subject","Body","From: (Name)","From: (Address)","From: (Type)","To:
(Name)","To: (Address)","To: (Type)","CC: (Name)","CC: (Address)","CC:
(Type)","BCC: (Name)","BCC: (Address)","BCC: (Type)","Billing
Information","Categories","Importance","Mileage","Sensitivity"

https://www.microsoft.com/en-us/trustcenter/compliance/SOX

Cheers

  A lot of obfuscation yammer.
  Note "there is no SOX certification or validation for cloud service
providers."
  WE are trustworthy because we paid off Azure "more than US $300
billion annual cash movement."
  Note they SAY nothing about data integrity: WHEN (day, time) was an
e-mail sent/received.
  It is called trace-ability.
  Critical.
Click to expand...
If you have hours to waste digging thru the tree of reports,be my guest.
Dozens of reports, lots of blather that does not address e-mail data
integrity per se.

NO mention of Office 365 "integrity", NO mention of e-mail export
"integrity" in fact, it is hard to find any mention of Office 365 except
en passant.
 
You must log in or register to reply here.

Welcome to EDABoard.com

Sponsor

Back
Top