Changes for page What an XWiki Security Review Should Actually Include
Last modified by Agnease on 2026/05/26 15:27
Summary
-
Page properties (2 modified, 0 added, 0 removed)
-
Objects (0 modified, 0 added, 1 removed)
Details
- Page properties
-
- Title
-
... ... @@ -1,1 +1,1 @@ 1 - What an XWikiSecurityReviewShould Actually Include1 +xwiki-security-review - 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 detectedproblems. It should produce a practical action158 + A useful security review should not only produce a list of 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,1 +1,0 @@ 1 -Learn what an XWiki security review should include: version status, access rights, authentication, extensions, custom code, infrastructure, backups and operational practices. - metaTitle
-
... ... @@ -1,1 +1,0 @@ 1 -What an XWiki Security Review Should Actually Include | Agnease