Difference between revisions of "Security/Collab"
m |
(Perhaps the start of a pseudo faq?) |
||
Line 1: | Line 1: | ||
− | {{BC| | + | {{BC|Security Center}} |
__FORCETOC__ | __FORCETOC__ | ||
<div class="col-md-12 ibox-content"> | <div class="col-md-12 ibox-content"> | ||
− | = | + | = Security Pointers and Tidbits = |
− | |||
− | == Security | + | The main jumping point for security is the [[Security Center]]. |
− | [[Security/Collab/ | + | |
+ | == Release Specific Settings == | ||
+ | * [[Security/Collab/86|ZCS 8.6 security settings]] | ||
+ | * [[Security/Collab/87|ZCS 8.7 security settings]] | ||
+ | |||
+ | = Odds and Ends = | ||
+ | Here are a few questions that come up from time to time... | ||
+ | |||
+ | * The ZM_TEST cookie is not setting the HttpOnly attribute, is this a problem? | ||
+ | ** The ZM_TEST cookie in ZCS is used solely to determine if cookies are enabled a the browser. There are no privileges associated with that cookie. As such, there is no inherent risk with not having an HttpOnly attribute on this cookie. |
Revision as of 22:10, 8 February 2016
Security Pointers and Tidbits
The main jumping point for security is the Security Center.
Release Specific Settings
Odds and Ends
Here are a few questions that come up from time to time...
- The ZM_TEST cookie is not setting the HttpOnly attribute, is this a problem?
- The ZM_TEST cookie in ZCS is used solely to determine if cookies are enabled a the browser. There are no privileges associated with that cookie. As such, there is no inherent risk with not having an HttpOnly attribute on this cookie.