Probably don't want to beg hackers to come and take your stuff.
npm install spectral-owasp-ruleset-test ![Stoplight Forest][stoplight_forest]
Scan an OpenAPI document to detect security issues. As OpenAPI is only describing the surface level of the API it cannot see what is happening in your code, but it can spot obvious issues and outdated standards being used.
``bash`
npm install --save -D @stoplight/spectral-owasp-ruleset
npm install --save -D @stoplight/spectral-cli
Create a local ruleset that extends the ruleset. In its most basic form this just tells Spectral what ruleset you want to use, but it will allow you to customise things, add your own rules, turn bits off if its causing trouble.
`
cd ~/src/
echo 'extends: ["@stoplight/spectral-owasp-ruleset"]' > .spectral.yaml
`
_If you're using VS Code or Stoplight Studio then the NPM modules will not be available. Instead you can use the CDN hosted version:_
`
echo 'extends: ["https://unpkg.com/@stoplight/spectral-owasp-ruleset@1.1.1/dist/ruleset.js"]' > .spectral.yaml
_Note: You need to use the full URL with CDN hosted rulesets because Spectral cannot follow redirects through extends._
Next, use Spectral CLI to lint against your OpenAPI description. Don't have any OpenAPI? Record some HTTP traffic to make OpenAPI and then you can switch to API Design-First going forwards.
`
spectral lint api/openapi.yaml
You should see some output like this:
`
/Users/phil/src/protect-earth-api/api/openapi.yaml
44:17 warning owasp:api3:2019-define-error-responses-400:400 response should be defined.. Missing responses[400] paths./upload.post.responses
44:17 warning owasp:api3:2019-define-error-responses-429:429 response should be defined.. Missing responses[429] paths./upload.post.responses
44:17 warning owasp:api3:2019-define-error-responses-500:500 response should be defined.. Missing responses[500] paths./upload.post.responses
45:15 error owasp:api4:2019-rate-limit All 2XX and 4XX responses should define rate limiting headers. paths./upload.post.responses[201]
47:15 error owasp:api4:2019-rate-limit All 2XX and 4XX responses should define rate limiting headers. paths./upload.post.responses[401]
53:15 error owasp:api4:2019-rate-limit All 2XX and 4XX responses should define rate limiting headers. paths./upload.post.responses[403]
59:15 error owasp:api4:2019-rate-limit All 2XX and 4XX responses should define rate limiting headers. paths./upload.post.responses[409]
65:15 error owasp:api4:2019-rate-limit All 2XX and 4XX responses should define rate limiting headers. paths./upload.post.responses[422]
193:16 information owasp:api2:2019-protection-global-safe This operation is not protected by any security scheme. paths./sites.get.security
210:16 information owasp:api2:2019-protection-global-safe This operation is not protected by any security scheme. paths./species.get.security
Now you have some things to work on for your API. Thankfully these are only at the warning and information` severity, and that is not going to fail continuous integration (unless you want them to).
There are a bunch of other rulesets you can use, or use for inspiration for your own rulesets and API Style Guides.
- Andrzej - Great rules contributed to the Adidas style guide.
- Roberto Polli - Created lots of excellent Spectral rules for API OAS Checker which aligned with the OWASP API rules.
This repository is licensed under the MIT license.
If you would like to thank us for creating Spectral, we ask that you [buy the world a tree][stoplight_forest].
[stoplight_forest]: https://ecologi.com/stoplightinc