Skip to content

Rationales #8

Open
Open
@erlkonig

Description

@erlkonig

Each thing in the list deserves a file on the rationale behind it, even if those are largely URLs.

Activity

alexchamberlain

alexchamberlain commented on Jul 9, 2017

@alexchamberlain

I agree that seeing the rationale would be great, but please don't do this within the checklist, as you probably don't want to read it every time you read the checklist.

netcode

netcode commented on Jul 9, 2017

@netcode
Member

A very good idea . May be we can start to make a seperate files as a reference to every check point.

StillLearnin

StillLearnin commented on Mar 25, 2018

@StillLearnin

How about wiki pages that are linked to from the list?

darioseidl

darioseidl commented on Oct 1, 2021

@darioseidl

Without a rational for each recommendation, the checklist is not very useful (to me at least).

Security is never perfect or absolute, so whether and how to secure something depends on how sensitive the data is and who you are protecting it from. And while some practices are widely accepted, there are disagreements about others. Take for example the discussions on Basic Auth and JWT in the issues on this repo. A rational for why the author(s) of this checklist recommend to use JWT Bearer Auth over Basic Auth would be good. (IMO, neither is perfect, but both can be good enough for some APIs)

montchr

montchr commented on Jun 14, 2022

@montchr

I agree that this list does not come across as useful to me. A security checklist asking its users to follow its advice without question paradoxically undermines the security-conscious process and mindset the checklist appears to support.

Maikuolan

Maikuolan commented on Jul 24, 2022

@Maikuolan
Collaborator

Anyone want to try having a go at this, make some PRs, etc?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

      Development

      No branches or pull requests

        Participants

        @netcode@erlkonig@alexchamberlain@montchr@StillLearnin

        Issue actions

          Rationales · Issue #8 · shieldfy/API-Security-Checklist