Skip to content

Commit 773cf7b

Browse files
authored
Update security and contact language (#332)
1 parent 3508eb3 commit 773cf7b

File tree

5 files changed

+20
-14
lines changed

5 files changed

+20
-14
lines changed

CONTRIBUTING.md

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -123,4 +123,6 @@ Docusaurus `plugin-client-redirects` plugin configuration in the larger `site/do
123123
If there are any outstanding questions about contributing to the Phylum documentation,
124124
they can be asked on the issue tracker: <https://github.com/phylum-dev/documentation/issues>.
125125
126-
As an alternative, you can also email `[email protected]`.
126+
As an alternative, you can also contact your Veracode customer success POC or [general support][veracode_support].
127+
128+
[veracode_support]: mailto:[email protected]

README.md

Lines changed: 3 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -39,6 +39,7 @@ Found a security issue in this repository? See the [security policy][security] f
3939

4040
## Questions/Issues
4141

42-
Please contact Veracode with any questions or issues.
42+
Please contact your Veracode customer success POC with any questions or issues.
43+
Contacting Veracode [general support][veracode_support] in another option.
4344

44-
Email: `phylum@veracode.com`
45+
[veracode_support]: mailto:support@veracode.com

SECURITY.md

Lines changed: 5 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -1,10 +1,11 @@
11
# Security Policy
22

3-
Phylum was founded by a team of security researchers at heart, and we take the security of our tooling seriously.
3+
At Veracode, security is job number one. We consider security in everything we
4+
do to ensure the trustworthiness of the tools and services we provide.
45

56
## Reporting a Vulnerability
67

78
We love coordinated disclosure!
8-
Please email [dl-phylum-engineering@veracode.com](mailto:dl-phylum-engineering@veracode.com) to start a conversation!
9-
We'll coordinate a secure communication mechanism first, then evaluate the reported issue(s)
10-
and keep you apprised each step of the way.
9+
Please email [grc@veracode.com](mailto:grc@veracode.com) to start a conversation!
10+
We'll coordinate a secure communication mechanism first, then evaluate the
11+
reported issue(s) and keep you apprised each step of the way.

docs/support/contact_us.md

Lines changed: 4 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,8 +1,9 @@
11
# Contact Us
22

33
We'd love to answer your questions or provide recommendations on your unique
4-
environment! Search our documentation, contact [support][phylum_support], or
5-
connect with our [sales team][vc_contact].
4+
environment! Search our documentation, contact your Veracode customer success
5+
POC, contact [general support][veracode_support], or connect with our
6+
[sales team][vc_contact].
67

7-
[phylum_support]: mailto:phylum@veracode.com
8+
[veracode_support]: mailto:support@veracode.com
89
[vc_contact]: https://www.veracode.com/contact-us/

docs/support/security.md

Lines changed: 5 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -1,10 +1,11 @@
11
# Security
22

3-
Phylum was founded by a team of security researchers at heart, and we take the security of our tooling seriously.
3+
At Veracode, security is job number one. We consider security in everything we
4+
do to ensure the trustworthiness of the tools and services we provide.
45

56
## Reporting security issues
67

78
We love coordinated disclosure!
8-
Please email [dl-phylum-engineering@veracode.com](mailto:dl-phylum-engineering@veracode.com) to start a conversation!
9-
We'll coordinate a secure communication mechanism first, then evaluate the reported issue(s) and keep you apprised each
10-
step of the way.
9+
Please email [grc@veracode.com](mailto:grc@veracode.com) to start a conversation!
10+
We'll coordinate a secure communication mechanism first, then evaluate the
11+
reported issue(s) and keep you apprised each step of the way.

0 commit comments

Comments
 (0)