6
6
1 . [ Incident Response Process] ( #process )
7
7
8
8
<a name =" reporting " ></a >
9
- ## Reporting security problems to Solana
9
+ ## Reporting security problems in the Solana Program Library
10
+
11
+ ** DO NOT CREATE A GITHUB ISSUE** to report a security problem.
12
+
13
+ Instead please use this [ Report a Vulnerability] ( https://github.com/solana-labs/solana-program-library/security/advisories/new ) link.
14
+ Provide a helpful title and detailed description of the problem.
15
+
16
+ If you haven't done so already, please ** enable two-factor auth** in your GitHub account.
17
+
18
+ Expect a response as fast as possible in the advisory, typically within 72 hours.
19
+
20
+ --
21
+
22
+ If you do not receive a response in the advisory, send an email to
23
+ [email protected] with the full URL of the advisory you have created. DO NOT
24
+ include attachments or provide detail sufficient for exploitation regarding the
25
+ security issue in this email. ** Only provide such details in the advisory** .
26
+
27
+ If you do not receive a response from
[email protected] please followup with
28
+ the team directly. You can do this in the ` #core-technology ` channel of the
29
+ [ Solana Tech discord server] ( https://solana.com/discord ) , by pinging the admins
30
+ in the channel and referencing the fact that you submitted a security problem.
10
31
11
- ** DO NOT CREATE AN ISSUE** to report a security problem. Instead, please send an
12
- email to
[email protected] and provide your github username so we can add you
13
- to a new draft security advisory for further discussion.
14
32
15
- Expect a response as fast as possible, typically within 72 hours.
16
33
17
34
<a name =" bounty " ></a >
18
35
## Security Bug Bounties
19
- We offer bounties for critical security issues. Please see the
20
- [ Solana Security Bug Bounties] ( https://github.com/solana-labs/solana/security/policy#security-bug-bounties )
36
+ The Solana Foundation offer bounties for critical Solana security issues. Please
37
+ see the [ Solana Security Bug
38
+ Bounties] ( https://github.com/solana-labs/solana/security/policy#security-bug-bounties )
21
39
for details on classes of bugs and payment amounts.
22
40
23
41
<a name =" scope " ></a >
24
42
## Scope
25
43
26
44
Only a subset of programs within the Solana Program Library repo are deployed to
27
- mainnet-beta and maintained by the team. Currently, this includes:
45
+ the Solana Mainnet Beta and maintained by the team. Currently, this includes:
28
46
29
47
* [ associated-token-account] ( https://github.com/solana-labs/solana-program-library/tree/master/associated-token-account/program )
30
48
* [ feature-proposal] ( https://github.com/solana-labs/solana-program-library/tree/master/feature-proposal/program )
@@ -51,4 +69,4 @@ may be affected and put you in touch the corresponding teams.
51
69
52
70
In case an incident is discovered or reported, the
53
71
[ Solana Security Incident Response Process] ( https://github.com/solana-labs/solana/security/policy#incident-response-process )
54
- will be followed to contain, respond and remediate.
72
+ will be followed to contain, respond and remediate.
0 commit comments