UNITED STATES
SECURITIES AND EXCHANGE COMMISSION
Washington, D.C. 20549
FORM 6-K
REPORT OF FOREIGN PRIVATE ISSUER
PURSUANT TO RULE 13a-16 OR 15d-16 OF
THE SECURITIES EXCHANGE ACT OF 1934
May 5, 2020
Commission file number:
1-14251
SAP SE
(Exact name of registrant as specified in its charter)
SAP EUROPEAN COMPANY
(Translation of registrant’s name into English)
Dietmar-Hopp-Allee 16
69190 Walldorf
Federal Republic of Germany
(Address of principal executive offices)
Indicate by check mark whether the registrant files or will file annual reports under cover of Form 20-F or Form 40-F.
Form 20-F x Form 40-F o
Indicate by check mark whether the registrant by furnishing the information contained in this Form is also thereby furnishing the information to the Commission pursuant to Rule 12g3-2(b) under the Securities Exchange Act of 1934.
Yes o No x
If “Yes” is marked, indicate below the file number assigned to the registrant in connection with Rule 12g3-2(b): 82- .
SAP SE
FORM 6-K
On May 4, 2020, SAP SE, (“SAP”), issued an ad hoc notification addressing gaps in connection with its contractual cybersecurity infrastructure terms relating to certain parts of its cloud products. The ad hoc notification is attached as Exhibit 99.1 hereto and incorporated by reference herein.
Any statements contained in this document that are not historical facts are forward-looking statements as defined in the U.S. Private Securities Litigation Reform Act of 1995. Words such as “anticipate,” “believe,” “estimate,” “expect,” “forecast,” “intend,” “may,” “plan,” “project,” “predict,” “should” and “will” and similar expressions as they relate to SAP are intended to identify such forward-looking statements. SAP undertakes no obligation to publicly update or revise any forward-looking statements. All forward-looking statements are subject to various risks and uncertainties that could cause actual results to differ materially from expectations. The factors that could affect SAP’s future financial results are discussed more fully in SAP’s filings with the U.S. Securities and Exchange Commission (the “SEC”), including SAP’s most recent Annual Report on Form 20-F filed with the SEC. Readers are cautioned not to place undue reliance on these forward-looking statements, which speak only as of their dates.
SIGNATURES
Pursuant to the requirements of the Securities Exchange Act of 1934, the registrant has duly caused this report to be signed on its behalf by the undersigned, thereunto duly authorized.
|
|
|
| |
|
|
SAP SE | ||
|
|
(Registrant) | ||
|
|
| ||
|
|
| ||
|
|
By: |
/s/ Christopher Sessar | |
|
|
|
Name: |
Dr. Christopher Sessar |
|
|
|
Title: |
Chief Accounting Officer |
|
|
|
|
|
|
|
|
|
|
|
|
By: |
/s/ Julia Zicke | |
|
|
|
Name: |
Dr. Julia Zicke |
|
|
|
Title: |
Head of Corporate External |
|
|
|
|
Reporting |
Date: May 5, 2020
Exhibit 99.1
SAP addresses gaps in connection with its contractual cybersecurity infrastructure terms relating to certain parts of its cloud products
Walldorf, May 4th, 2020. SAP SE (NYSE: SAP) continuously reviews and optimizes its cybersecurity infrastructure. The company has identified that some of its cloud products do not meet one or several contractually agreed or statutory IT security standards at present. Specifically, the affected products are limited to the acquired entity products SAP Success Factors, SAP Concur, SAP/CallidusCloud Commissions, SAP/Callidus Cloud CPQ; as well as SAP C4C/Sales Cloud, SAP Cloud Platform and SAP Analytics Cloud.
These findings were not identified in response to a security incident. As SAP continues with its review, it does not believe that any customer data has been compromised as a result of these issues. In an effort to ensure that the affected products meet relevant terms and conditions and in addition to technical remediation, SAP has decided to update its security-related terms and conditions. These remain in line with market peers.
Moreover, SAP has initiated remediation of the identified areas of shortcomings against contractually agreed or statutory standards and will proceed expeditiously. Remediation will largely be completed in the second quarter 2020. The expenses related to the remediation are expected to be covered within the range of SAP’s current 2020 financial outlook.
The executive board of SAP SE has decided today that SAP will inform and support the affected customers individually — approximately 9 percent of SAP’s 440,000 customers.
# # #
Any statements contained in this document that are not historical facts are forward-looking statements as defined in the U.S. Private Securities Litigation Reform Act of 1995. Words such as “anticipate,” “believe,” “estimate,” “expect,” “forecast,” “intend,” “may,” “plan,” “project,” “predict,” “should” and “will” and similar expressions as they relate to SAP are intended to identify such forward-looking statements. SAP undertakes no obligation to publicly update or revise any forward-looking statements. All forward-looking statements are subject to various risks and uncertainties that could cause actual results to differ materially from expectations. The factors that could affect SAP’s future financial results are discussed more fully in SAP’s filings with the U.S. Securities and Exchange Commission (“SEC”), including SAP’s most recent Annual Report on Form 20-F filed with the SEC. Readers are cautioned not to place undue reliance on these forward-looking statements, which speak only as of their dates.
© 2020 SAP SE. All rights reserved.
SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP SE in Germany and other countries. Please see https://www.sap.com/copyright for additional trademark information and notices.