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)
Details
- Page properties
-
- Content
-
... ... @@ -122,13 +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 127 - <a href="$xwiki.getURL('resources.xwiki-access-rights-governance')">why XWiki access rights need a clear governance model</a>. 128 - For a practical starting point, see 129 - <a href="$xwiki.getURL('resources.xwiki-access-rights-review')">how to start an XWiki access-rights review</a>. 130 - </p> 131 - 132 132 <h3>3. Authentication and identity management</h3> 133 133 <p> 134 134 Authentication should be reviewed beyond the simple question of whether users can log in. LDAP, Active ... ... @@ -239,16 +239,6 @@ 239 239 permissions, extensions, customizations and recovery procedures were configured years earlier. 240 240 </p> 241 241 242 - <div class="resource-note"> 243 - <p> 244 - <strong>Security review series:</strong> 245 - this article is the main overview. You can also read 246 - <a href="$xwiki.getURL('resources.xwiki-access-rights-governance')">why XWiki access rights need a clear governance model</a>. 247 - Future topics will cover authentication and access control, script and programming rights, backup validation, 248 - extension review and operational practices. 249 - </p> 250 - </div> 251 - 252 252 <h2 id="security-review-faq">XWiki security review FAQ</h2> 253 253 254 254 <h3>What should an XWiki security review include?</h3> ... ... @@ -288,7 +288,6 @@ 288 288 <div class="resource-note"> 289 289 <p> 290 290 Related resources: 291 - <a href="$xwiki.getURL('resources.xwiki-access-rights-governance')">why XWiki access rights need a clear governance model</a>, 292 292 <a href="$xwiki.getURL('resources.why-upgrade-xwiki')">why regular XWiki upgrades matter</a> 293 293 and 294 294 <a href="$xwiki.getURL('resources.xwiki-custom-development')">how to keep XWiki custom development maintainable across upgrades</a>.