Update documentation for communicating discovered security vulnerabilities (#657)

Aligning to recently published common SECURITY.md file available at
https://github.com/microsoft/microsoft.github.io/blob/master/SECURITY.MD

README.md

@@ -64,12 +64,7 @@ for your use. The mock data will be clearly identifiable as it references planet
 and remains static regardless of selected inputs.
 
 ## Reporting Security Issues
-Security issues and bugs should be reported privately, via email, to the
+Please refer to [SECURITY.md](./SECURITY.md).
-Microsoft Security Response Center (MSRC) at <[secure@microsoft.com](mailto:secure@microsoft.com)>.
-You should receive a response within 24 hours. If for some reason you do not, please follow up via
-email to ensure we received your original message. Further information, including the
-[MSRC PGP](https://technet.microsoft.com/en-us/security/dn606155) key, can be found in the
-[Security TechCenter](https://technet.microsoft.com/en-us/security/default).
 
 ## License
 Copyright (c) Microsoft Corporation. All rights reserved.

SECURITY.md

@@ -0,0 +1,48 @@
+<!-- BEGIN MICROSOFT SECURITY.MD V0.0.1 BLOCK -->
+
+## Security
+
+Microsoft takes the security of our software products and services seriously, which includes all
+source code repositories managed through our GitHub organizations, which include
+[Microsoft](https://github.com/Microsoft), [Azure](https://github.com/Azure),
+[DotNet](https://github.com/dotnet), [AspNet](https://github.com/aspnet),
+[Xamarin](https://github.com/xamarin), and [many more](https://opensource.microsoft.com/).
+
+If you believe you have found a security vulnerability in any Microsoft-owned repository that meets
+Microsoft's [definition](https://docs.microsoft.com/en-us/previous-versions/tn-archive/cc751383(v=technet.10))
+of a security vulnerability, please report it to us as described below.
+
+## Reporting Security Issues
+
+**Please do not report security vulnerabilities through public GitHub issues.** Instead, please
+report them to the Microsoft Security Response Center at [secure@microsoft.com](mailto:secure@microsoft.com).
+If possible, encrypt your message with our PGP key; please download it from the
+[Microsoft Security Response Center PGP Key page](https://technet.microsoft.com/en-us/security/dn606155).
+
+You should receive a response within 24 hours. If for some reason you do not, please follow up via
+email to ensure we received your original message. Additional information can be found at
+[microsoft.com/msrc](https://www.microsoft.com/msrc).
+
+Please include the requested information listed below (as much as you can provide) to help us better
+understand the nature and scope of the possible issue:
+
+  * Type of issue (e.g. buffer overflow, SQL injection, cross-site scripting, etc.)
+  * Full paths of source file(s) related to the manifestation of the issue
+  * The location of the affected source code (tag/branch/commit or direct URL)
+  * Any special configuration required to reproduce the issue
+  * Step-by-step instructions to reproduce the issue
+  * Proof-of-concept or exploit code (if possible)
+  * Impact of the issue, including how an attacker might exploit the issue
+
+This information will help us triage your report more quickly.
+
+## Preferred Languages
+
+We prefer all communications to be in English.
+
+## Policy
+
+Microsoft follows the principle of
+[Coordinated Vulnerability Disclosure](https://www.microsoft.com/en-us/msrc/cvd).
+
+<!-- END MICROSOFT SECURITY.MD BLOCK -->