Update security and contact language

CONTRIBUTING.md

@@ -123,4 +123,6 @@ Docusaurus `plugin-client-redirects` plugin configuration in the larger `site/do
 If there are any outstanding questions about contributing to the Phylum documentation,
 they can be asked on the issue tracker: <https://github.com/phylum-dev/documentation/issues>.
 
-As an alternative, you can also email `phylum@veracode.com`.
+As an alternative, you can also contact your Veracode customer success POC or [general support][veracode_support].
+
+[veracode_support]: mailto:support@veracode.com

README.md

@@ -39,6 +39,7 @@ Found a security issue in this repository? See the [security policy][security] f
 
 ## Questions/Issues
 
-Please contact Veracode with any questions or issues.
+Please contact your Veracode customer success POC with any questions or issues.
+Contacting Veracode [general support][veracode_support] in another option.
 
-Email: `phylum@veracode.com`
+[veracode_support]: mailto:support@veracode.com

SECURITY.md

@@ -1,10 +1,11 @@
 # Security Policy
 
-Phylum was founded by a team of security researchers at heart, and we take the security of our tooling seriously.
+At Veracode, security is job number one. We consider security in everything we
+do to ensure the trustworthiness of the tools and services we provide.
 
 ## Reporting a Vulnerability
 
 We love coordinated disclosure!
-Please email [dl-phylum-engineering@veracode.com](mailto:dl-phylum-engineering@veracode.com) to start a conversation!
-We'll coordinate a secure communication mechanism first, then evaluate the reported issue(s)
-and keep you apprised each step of the way.
+Please email [grc@veracode.com](mailto:grc@veracode.com) to start a conversation!
+We'll coordinate a secure communication mechanism first, then evaluate the
+reported issue(s) and keep you apprised each step of the way.

docs/support/contact_us.md

@@ -1,8 +1,9 @@
 # Contact Us
 
 We'd love to answer your questions or provide recommendations on your unique
-environment! Search our documentation, contact [support][phylum_support], or
-connect with our [sales team][vc_contact].
+environment! Search our documentation, contact your Veracode customer success
+POC, contact [general support][veracode_support], or connect with our
+[sales team][vc_contact].
 
-[phylum_support]: mailto:phylum@veracode.com
+[veracode_support]: mailto:support@veracode.com
 [vc_contact]: https://www.veracode.com/contact-us/

docs/support/security.md

@@ -1,10 +1,11 @@
 # Security
 
-Phylum was founded by a team of security researchers at heart, and we take the security of our tooling seriously.
+At Veracode, security is job number one. We consider security in everything we
+do to ensure the trustworthiness of the tools and services we provide.
 
 ## Reporting security issues
 
 We love coordinated disclosure!
-Please email [dl-phylum-engineering@veracode.com](mailto:dl-phylum-engineering@veracode.com) to start a conversation!
-We'll coordinate a secure communication mechanism first, then evaluate the reported issue(s) and keep you apprised each
-step of the way.
+Please email [grc@veracode.com](mailto:grc@veracode.com) to start a conversation!
+We'll coordinate a secure communication mechanism first, then evaluate the
+reported issue(s) and keep you apprised each step of the way.