Skip to content

Commit dd93e2c

Browse files
Security - move auth section here.
1 parent fe6ce8f commit dd93e2c

File tree

1 file changed

+9
-1
lines changed

1 file changed

+9
-1
lines changed

docs/security/operations.md

Lines changed: 9 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -19,4 +19,12 @@ When an incident is identified the security operations team performs triage and
1919

2020
Polygon Labs carefully considers when, how and who to communicate with during incident response. Impacted stakeholders are sent notifications in a timely manner to ensure they can take reasonable steps to protect their information if necessary. Polygon Labs also makes every effort to work with law enforcement to the degree required by the laws of the jurisdictions that we operate in, which may be different depending on the nature of the cyber security incident.
2121

22-
In order to ensure the incident response process remains relevant, we conduct regular incident response exercises if no real security incident has occurred after a given period.
22+
In order to ensure the incident response process remains relevant, we conduct regular incident response exercises if no real security incident has occurred after a given period.
23+
24+
**Authentication & Access Control**
25+
26+
Polygon Labs establishes standards for authentication & access control in its information security policy and information security standards documents.
27+
28+
To ensure the security of our corporate systems, all employees must adhere to strict password requirements. Passwords should be changed regularly according to our guidelines and two-factor authentication is mandatory for accessing sensitive systems. Default, shared, or easily guessable passwords are strictly prohibited.
29+
30+
Polygon Labs performs entitlement reviews for sensitive systems on a yearly basis. Where applicable and available, systems are accessed via single sign-on (SSO).

0 commit comments

Comments
 (0)