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,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 ... ... @@ -236,16 +236,6 @@ 236 236 permissions, extensions, customizations and recovery procedures were configured years earlier. 237 237 </p> 238 238 239 - <div class="resource-note"> 240 - <p> 241 - <strong>Security review series:</strong> 242 - this article is the main overview. You can also read 243 - <a href="$xwiki.getURL('resources.xwiki-access-rights-governance')">why XWiki access rights need a clear governance model</a>. 244 - Future topics will cover authentication and access control, script and programming rights, backup validation, 245 - extension review and operational practices. 246 - </p> 247 - </div> 248 - 249 249 <h2 id="security-review-faq">XWiki security review FAQ</h2> 250 250 251 251 <h3>What should an XWiki security review include?</h3> ... ... @@ -285,7 +285,6 @@ 285 285 <div class="resource-note"> 286 286 <p> 287 287 Related resources: 288 - <a href="$xwiki.getURL('resources.xwiki-access-rights-governance')">why XWiki access rights need a clear governance model</a>, 289 289 <a href="$xwiki.getURL('resources.why-upgrade-xwiki')">why regular XWiki upgrades matter</a> 290 290 and 291 291 <a href="$xwiki.getURL('resources.xwiki-custom-development')">how to keep XWiki custom development maintainable across upgrades</a>.