Skip to content

Commit 1e6b486

Browse files
jokayPeerRich
andauthored
Fix markdownlint issues (#9497)
Co-authored-by: Peer Richelsen <peeroke@gmail.com>
1 parent 617cf9c commit 1e6b486

File tree

1 file changed

+36
-18
lines changed

1 file changed

+36
-18
lines changed

SECURITY.md

+36-18
Original file line numberDiff line numberDiff line change
@@ -1,39 +1,57 @@
11
# Security
22

3-
Contact: security@cal.com
3+
Contact: [security@cal.com](mailto:security@cal.com)
44

55
Based on [https://supabase.com/.well-known/security.txt](https://supabase.com/.well-known/security.txt)
66

7-
At Cal.com, we consider the security of our systems a top priority. But no matter how much effort we put into system security, there can still be vulnerabilities present.
7+
At Cal.com, we consider the security of our systems a top priority. But no
8+
matter how much effort we put into system security, there can still be
9+
vulnerabilities present.
810

9-
If you discover a vulnerability, we would like to know about it so we can take steps to address it as quickly as possible. We would like to ask you to help us better protect our clients and our systems.
11+
If you discover a vulnerability, we would like to know about it so we can take
12+
steps to address it as quickly as possible. We would like to ask you to help us
13+
better protect our clients and our systems.
1014

11-
## Out of scope vulnerabilities:
15+
## Out of scope vulnerabilities
1216

1317
- Clickjacking on pages with no sensitive actions.
1418
- Unauthenticated/logout/login CSRF.
1519
- Attacks requiring MITM or physical access to a user's device.
1620
- Any activity that could lead to the disruption of our service (DoS).
17-
- Content spoofing and text injection issues without showing an attack vector/without being able to modify HTML/CSS.
21+
- Content spoofing and text injection issues without showing an attack
22+
vector/without being able to modify HTML/CSS.
1823
- Email spoofing
1924
- Missing DNSSEC, CAA, CSP headers
2025
- Lack of Secure or HTTP only flag on non-sensitive cookies
2126
- Deadlinks
2227

23-
## Please do the following:
28+
## Please do the following
2429

2530
- E-mail your findings to [security@cal.com](mailto:security@cal.com).
26-
- Do not run automated scanners on our infrastructure or dashboard. If you wish to do this, contact us and we will set up a sandbox for you.
27-
- Do not take advantage of the vulnerability or problem you have discovered, for example by downloading more data than necessary to demonstrate the vulnerability or deleting or modifying other people's data,
31+
- Do not run automated scanners on our infrastructure or dashboard. If you wish
32+
to do this, contact us and we will set up a sandbox for you.
33+
- Do not take advantage of the vulnerability or problem you have discovered,
34+
for example by downloading more data than necessary to demonstrate the
35+
vulnerability or deleting or modifying other people's data,
2836
- Do not reveal the problem to others until it has been resolved,
29-
- Do not use attacks on physical security, social engineering, distributed denial of service, spam or applications of third parties,
30-
- Do provide sufficient information to reproduce the problem, so we will be able to resolve it as quickly as possible. Usually, the IP address or the URL of the affected system and a description of the vulnerability will be sufficient, but complex vulnerabilities may require further explanation.
31-
32-
## What we promise:
33-
34-
- We will respond to your report within 3 business days with our evaluation of the report and an expected resolution date,
35-
- If you have followed the instructions above, we will not take any legal action against you in regard to the report,
36-
- We will handle your report with strict confidentiality, and not pass on your personal details to third parties without your permission,
37+
- Do not use attacks on physical security, social engineering, distributed
38+
denial of service, spam or applications of third parties,
39+
- Do provide sufficient information to reproduce the problem, so we will be
40+
able to resolve it as quickly as possible. Usually, the IP address or the URL
41+
of the affected system and a description of the vulnerability will be
42+
sufficient, but complex vulnerabilities may require further explanation.
43+
44+
## What we promise
45+
46+
- We will respond to your report within 3 business days with our evaluation of
47+
the report and an expected resolution date,
48+
- If you have followed the instructions above, we will not take any legal
49+
action against you in regard to the report,
50+
- We will handle your report with strict confidentiality, and not pass on your
51+
personal details to third parties without your permission,
3752
- We will keep you informed of the progress towards resolving the problem,
38-
- In the public information concerning the problem reported, we will give your name as the discoverer of the problem (unless you desire otherwise), and
39-
- We strive to resolve all problems as quickly as possible, and we would like to play an active role in the ultimate publication on the problem after it is resolved.
53+
- In the public information concerning the problem reported, we will give your
54+
name as the discoverer of the problem (unless you desire otherwise), and
55+
- We strive to resolve all problems as quickly as possible, and we would like
56+
to play an active role in the ultimate publication on the problem after it
57+
is resolved.

0 commit comments

Comments
 (0)