Changes for page What an XWiki Security Review Should Actually Include
Last modified by Alex Cotiuga on 2026/07/13 06:44
From version 1.3
edited by Alex Cotiuga
on 2026/05/26 07:46
on 2026/05/26 07:46
Change comment:
There is no comment for this version
To version 1.7
edited by Alex Cotiuga
on 2026/05/26 09:14
on 2026/05/26 09:14
Change comment:
There is no comment for this version
Summary
-
Page properties (1 modified, 0 added, 0 removed)
-
Objects (0 modified, 1 added, 0 removed)
Details
- Page properties
-
- Content
-
... ... @@ -155,7 +155,7 @@ 155 155 <h2 id="review-output">What the review should produce</h2> 156 156 157 157 <p> 158 - A useful security review should not only produce a list of problems. It should produce a practical action 158 + A useful security review should not only produce a list of detected problems. It should produce a practical action 159 159 plan. Each finding should explain the risk, the affected area, the recommended action and the priority. 160 160 </p> 161 161
- Agnease.Code.SEODetailsClass[0]
-
- metaDescription
-
... ... @@ -1,0 +1,1 @@ 1 +Learn what an XWiki security review should include: version status, access rights, authentication, extensions, custom code, infrastructure, backups and operational practices. - metaTitle
-
... ... @@ -1,0 +1,1 @@ 1 +What an XWiki Security Review Should Actually Include | Agnease