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.

Sign up for GitHub

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

Corrected Second sentence in API security section #45

Merged
merged 4 commits into from
Mar 29, 2021
Merged

Corrected Second sentence in API security section #45

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
6b5e85e
Update api-security.md
rahariya Jul 31, 2020
1648f22
Corrected grammatical mistakes
rahariya Jul 31, 2020
0d409ba
clean as original national api standards master branch
peeyush-rahariya-gtp Jul 31, 2020
0f09ecc
Corrected Second sentence in API security section
peeyush-rahariya-gtp Aug 7, 2020
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions .gitignore
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,3 +1,4 @@
node_modules
target
node_modules
/.vs/slnx.sqlite
4 changes: 2 additions & 2 deletions sections/api-security.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -5,7 +5,7 @@ ______________________________________________________________________________

Applying the right level of security will allow your APIs to perform well without compromising on the security risk.

To secure your APIs the security standards are grouped into three categories: Design, Transport, and Authentication and Authorisation.
To secure your APIs the security standards are grouped into three categories: Design, Transport, and Authentication & Authorisation.

At minimum the security standards that are defined here **MUST** be applied. Further security considerations may apply depending on the API design and requirements – refer to our [API Design Considerations section](getting-started.html#how-to-apply-the-design-standard) for more details.

Expand Down Expand Up @@ -128,4 +128,4 @@ It is preferable to use the security policy features available in the WoG API Ga
| OAUTH | Filter -\> OAUTH | OAUTH can be used for authorizing the consumers | Optional as it depends on business requirements |
| CORS | Listeners-\>Path | CORS can be restricted at path level | Recommended |

The WoG API Team can provide advice on which API Gateway security policies should be applied.
The WoG API Team can provide advice on which API Gateway security policies should be applied.