Changes for page What an XWiki Security Review Should Actually Include
Last modified by Agnease on 2026/06/08 18:44
Summary
-
Page properties (1 modified, 0 added, 0 removed)
-
Attachments (0 modified, 0 added, 1 removed)
Details
- Page properties
-
- Content
-
... ... @@ -122,10 +122,6 @@ 122 122 of small exceptions that nobody reviewed later. 123 123 </p> 124 124 125 - <p> 126 - For a deeper look at this topic, see <a href="$xwiki.getURL('resources.xwiki-access-rights-governance')">why XWiki access rights need a clear governance model</a>. 127 - </p> 128 - 129 129 <h3>3. Authentication and identity management</h3> 130 130 <p> 131 131 Authentication should be reviewed beyond the simple question of whether users can log in. LDAP, Active ... ... @@ -167,15 +167,6 @@ 167 167 knows what is included, how long recovery would take or whether the restore process has ever been tested. 168 168 </p> 169 169 170 - <div class="resource-inline-cta"> 171 - <p> 172 - <strong>Need a clearer view of your XWiki security posture?</strong> 173 - A structured review can check versions, access rights, authentication, 174 - extensions, custom code, infrastructure, backups and operational practices. 175 - </p> 176 - <a class="btn btn-secondary" href="$xwiki.getURL('contact.WebHome')">Request a security review</a> 177 - </div> 178 - 179 179 <h2 id="security-checklist">XWiki security review checklist</h2> 180 180 181 181 <p>
- xwiki-security-review.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Admin - Size
-
... ... @@ -1,1 +1,0 @@ 1 -1.3 MB - Content