You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Radu Cotescu (Jira)" <ji...@apache.org> on 2020/01/16 16:53:00 UTC

[jira] [Comment Edited] (SLING-8866) Add reporting info in the XSS Protection API bundle

    [ https://issues.apache.org/jira/browse/SLING-8866?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17017298#comment-17017298 ] 

Radu Cotescu edited comment on SLING-8866 at 1/16/20 4:52 PM:
--------------------------------------------------------------

Implemented in [acaefc4|https://github.com/apache/sling-org-apache-sling-xss/commit/acaefc493eca19e3efbfef86fb712bb0db6bb57f]:
* added a counter metric (sling:xss.invalid_hrefs) to track the number of invalid URLs detected by org.apache.sling.xss.XSSFilter#isValidHref
* enhanced the webconsole plugin to provide a detailed report of the blocked URLs
* allow a system administrator to download the active AntiSamy configuration
* expose JSON / XML endpoints to retrieve the current status of the XSS library / the active AntiSamy configuration

Currently the metrics don't need to be configured based on paths.


was (Author: radu.cotescu):
Implemented in [acaefc4|https://github.com/apache/sling-org-apache-sling-xss/commit/acaefc493eca19e3efbfef86fb712bb0db6bb57f].

> Add reporting info in the XSS Protection API bundle
> ---------------------------------------------------
>
>                 Key: SLING-8866
>                 URL: https://issues.apache.org/jira/browse/SLING-8866
>             Project: Sling
>          Issue Type: Improvement
>          Components: XSS Protection API
>            Reporter: Radu Cotescu
>            Assignee: Radu Cotescu
>            Priority: Major
>             Fix For: XSS Protection API 2.2.0
>
>          Time Spent: 1h 50m
>  Remaining Estimate: 0h
>
> The XSS Protection API should be enhanced to provide some reporting about invalid URLs in order to allow operators of a Sling instance to monitor the state of the system (e.g. incorrect AntiSamy configurations, attacks, DOS attempts, etc.).
> The following ideas should be taken into consideration:
> # add last X blocked expressions to the Sling XSS Web Console page
> # generate blocked metrics, based on configurable paths, e.g. {{/libs}}, {{/apps}}, {{/content}}.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)