Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Enforcing web platform security features #235

Open
Malvoz opened this issue Oct 22, 2020 · 0 comments
Open

Enforcing web platform security features #235

Malvoz opened this issue Oct 22, 2020 · 0 comments
Labels
discussion: cost-benefit tags all aspects of the priorities sections and cost-benefit tags section: map viewer Capabilities & use cases for declarative map viewer widgets status: suggestion this issue discusses a suggested addition to the report, that is not yet in the draft

Comments

@Malvoz
Copy link
Member

Malvoz commented Oct 22, 2020

Security features could be more easily enforced by authors in regards to maps/map data in a native implementation.

It'd be great if we could mention such features perhaps with a label of "Privacy/Security: potential improvement" in the conclusion of the Capability: Embed an interactive map viewer, using HTML markup(?).

Here are three examples of security features to showcase how developers may benefit (and in turn improve security/privacy for the end-user, as these measurements would be easier to apply) in a native implementation:

  • Content Security Policy

    The groups' custom map component requires a rather lengthy ("strict" host-based) Content Security Policy:

    Content-Security-Policy: default-src 'self';
                             connect-src 'self' geogratis.gc.ca;
                             img-src 'self' geoappext.nrcan.gc.ca data:;
                             style-src 'self' 'sha256-P4nvk0+qiIx5/zAz4EEwcyUE3w/JYhx1p6AynA4FauI='
                                              'sha256-eo5LoOQ6vGE1TgplgVKmRN6i3TkRxeOJ5YVVeFUBevc='
                                              'sha256-gWLDNLsycvRcRqEScFHdCYPrg1OzxzQBXX7qYFP1Ww0='
    

    (and Leaflet users have expressed some dissatisfaction with the CSP modifications needed to embed their maps.)

    whereas in a native implementation perhaps only one directive could be sufficient (e.g. layer-src):

    Content-Security-Policy: default-src 'self';
                             layer-src geogratis.gc.ca
    

For the capability's conclusion section I hope we can at least briefly mention/list all or some of the above security features.

@Malvoz Malvoz added discussion: cost-benefit tags all aspects of the priorities sections and cost-benefit tags section: map viewer Capabilities & use cases for declarative map viewer widgets status: suggestion this issue discusses a suggested addition to the report, that is not yet in the draft labels Oct 22, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
discussion: cost-benefit tags all aspects of the priorities sections and cost-benefit tags section: map viewer Capabilities & use cases for declarative map viewer widgets status: suggestion this issue discusses a suggested addition to the report, that is not yet in the draft
Projects
None yet
Development

No branches or pull requests

1 participant