Skip to Content
Last modified by Agnease on 2026/06/08 18:44
From version 1.8
edited by Agnease
on 2026/05/26 09:29
Change comment: There is no comment for this version
To version 3.11
edited by Agnease
on 2026/06/08 18:30
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -45,6 +45,11 @@
45 45   </p>
46 46  
47 47   <p>
48 + An XWiki security review is a practical audit of the platform configuration, access model,
49 + authentication setup, installed extensions, custom code, infrastructure and recovery procedures.
50 + </p>
51 +
52 + <p>
48 48   Security risks are often hidden in less visible areas: outdated versions, inherited permissions,
49 49   forgotten administrator accounts, overly powerful rights, old extensions, undocumented scripts,
50 50   weak fallback access or backup assumptions that were never tested.
... ... @@ -122,6 +122,13 @@
122 122   of small exceptions that nobody reviewed later.
123 123   </p>
124 124  
130 + <p>
131 + For a deeper look at this topic, see
132 + <a href="$xwiki.getURL('resources.xwiki-access-rights-governance')">why XWiki access rights need a clear governance model</a>.
133 + For a practical starting point, see
134 + <a href="$xwiki.getURL('resources.xwiki-access-rights-review')">how to start an XWiki access-rights review</a>.
135 + </p>
136 +
125 125   <h3>3. Authentication and identity management</h3>
126 126   <p>
127 127   Authentication should be reviewed beyond the simple question of whether users can log in. LDAP, Active
... ... @@ -163,6 +163,15 @@
163 163   knows what is included, how long recovery would take or whether the restore process has ever been tested.
164 164   </p>
165 165  
178 + <div class="resource-inline-cta">
179 + <p>
180 + <strong>Need a clearer view of your XWiki security posture?</strong>
181 + A structured review can check versions, access rights, authentication,
182 + extensions, custom code, infrastructure, backups and operational practices.
183 + </p>
184 + <a class="btn btn-default" href="$xwiki.getURL('contact.WebHome')">Request a security review</a>
185 + </div>
186 +
166 166   <h2 id="security-checklist">XWiki security review checklist</h2>
167 167  
168 168   <p>
... ... @@ -223,49 +223,87 @@
223 223   permissions, extensions, customizations and recovery procedures were configured years earlier.
224 224   </p>
225 225  
247 + <div class="resource-note related-resources">
248 + <p><strong>Security review series:</strong></p>
249 + <ul>
250 + <li>
251 + <a href="$xwiki.getURL('resources.xwiki-security-review')">What an XWiki security review should actually include</a>
252 + </li>
253 + <li>
254 + <a href="$xwiki.getURL('resources.xwiki-access-rights-governance')">Why XWiki access rights need a clear governance model</a>
255 + </li>
256 + <li>
257 + <a href="$xwiki.getURL('resources.xwiki-access-rights-review')">How to start an XWiki access-rights review</a>
258 + </li>
259 + </ul>
260 + <p>
261 + Future topics will cover authentication and access control, script and programming rights,
262 + backup validation, extension review and operational practices.
263 + </p>
264 + </div>
265 +
226 226   <h2 id="security-review-faq">XWiki security review FAQ</h2>
227 227  
228 - <h3>What should an XWiki security review include?</h3>
229 - <p>
230 - An XWiki security review should include the installed XWiki version, upgrade path,
231 - access rights, groups, authentication setup, installed extensions, custom code,
232 - infrastructure, backups, restore expectations and operational procedures.
233 - </p>
268 + <details class="resource-faq-item" open>
269 + <summary>What should an XWiki security review include?</summary>
270 + <p>
271 + An XWiki security review should include the installed XWiki version, upgrade path,
272 + access rights, groups, authentication setup, installed extensions, custom code,
273 + infrastructure, backups, restore expectations and operational procedures.
274 + </p>
275 + </details>
234 234  
235 - <h3>Is an updated XWiki instance automatically secure?</h3>
236 - <p>
237 - No. Updating XWiki is important, but security also depends on permissions,
238 - authentication, extensions, custom code, infrastructure configuration, backups
239 - and how the instance is maintained.
240 - </p>
277 + <details class="resource-faq-item">
278 + <summary>Is an updated XWiki instance automatically secure?</summary>
279 + <p>
280 + No. Updating XWiki is important, but security also depends on permissions,
281 + authentication, extensions, custom code, infrastructure configuration, backups
282 + and how the instance is maintained.
283 + </p>
284 + </details>
241 241  
242 - <h3>Does SSO solve XWiki access control?</h3>
243 - <p>
244 - No. SSO helps authenticate users, but access control still depends on XWiki groups,
245 - inherited permissions, page-level rights and administrative privileges.
246 - </p>
286 + <details class="resource-faq-item">
287 + <summary>Does SSO solve XWiki access control?</summary>
288 + <p>
289 + No. SSO helps authenticate users, but access control still depends on XWiki groups,
290 + inherited permissions, page-level rights and administrative privileges.
291 + </p>
292 + </details>
247 247  
248 - <h3>Why should custom code be reviewed?</h3>
249 - <p>
250 - Custom scripts, templates, macros, UI extensions and Java components can affect
251 - permissions, workflows, rendering, integrations and upgrade behavior. They should
252 - be identified, documented and tested.
253 - </p>
294 + <details class="resource-faq-item">
295 + <summary>Why should custom code be reviewed?</summary>
296 + <p>
297 + Custom scripts, templates, macros, UI extensions and Java components can affect
298 + permissions, workflows, rendering, integrations and upgrade behavior. They should
299 + be identified, documented and tested.
300 + </p>
301 + </details>
254 254  
255 - <h3>When should an XWiki security review be done?</h3>
256 - <p>
257 - A review is useful before a major upgrade, after years of organic growth, after
258 - authentication changes, before exposing the wiki more broadly, or when the instance
259 - becomes business-critical.
260 - </p>
261 -
262 - <div class="resource-note">
303 + <details class="resource-faq-item">
304 + <summary>When should an XWiki security review be done?</summary>
263 263   <p>
264 - Related resources:
265 - <a href="$xwiki.getURL('resources.why-upgrade-xwiki')">why regular XWiki upgrades matter</a>
266 - and
267 - <a href="$xwiki.getURL('resources.xwiki-custom-development')">how to keep XWiki custom development maintainable across upgrades</a>.
306 + A review is useful before a major upgrade, after years of organic growth, after
307 + authentication changes, before exposing the wiki more broadly, or when the instance
308 + becomes business-critical.
268 268   </p>
310 + </details>
311 +
312 + <div class="resource-note related-resources">
313 + <p><strong>Related resources:</strong></p>
314 + <ul>
315 + <li>
316 + <a href="$xwiki.getURL('resources.xwiki-access-rights-governance')">Why XWiki access rights need a clear governance model</a>
317 + </li>
318 + <li>
319 + <a href="$xwiki.getURL('resources.xwiki-access-rights-review')">How to start an XWiki access-rights review</a>
320 + </li>
321 + <li>
322 + <a href="$xwiki.getURL('resources.why-upgrade-xwiki')">Why regular XWiki upgrades matter</a>
323 + </li>
324 + <li>
325 + <a href="$xwiki.getURL('resources.xwiki-custom-development')">How to keep XWiki custom development maintainable across upgrades</a>
326 + </li>
327 + </ul>
269 269   </div>
270 270  
271 271   <div class="resource-cta">
xwiki-security-review.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Admin
Size
... ... @@ -1,0 +1,1 @@
1 +1.3 MB
Content