docusignapi - Security Issues with Docusign API -


we have developed app in salesforce uses docusign web service api (https://demo.docusign.net/api/3.0/dsapi.asmx development , https://www.docusign.net/api/3.0/dsapi.asmx production). found few vulnerabilities when did security scanning on both apis. used zap tool security scanning , revealed below vulnerabilities:

  1. x-frame-options header not set
  2. incomplete or no cache-control , pragma http header set
  3. web browser xss protection not enabled
  4. x-content-type-options header missing

can these issues fixed on web services or there document proves these false positive?

thanks

zap, automated scanners, @ finding common oversights , comparing applications best practices. unfortunately, fail consider larger scenario @ hand. setting correct x-headers right scenarios important protection against common attacks click-jacking , xss in client-server web flows, inform user's browser actions should permitted or not. attacks not relevant in server server api flow, however, these should considered false positives. thank bringing these our attention, however, docusign continuously investing in our platform's security , appreciate scrutiny.


Comments

Popular posts from this blog

IF statement in MySQL trigger -

c++ - What does MSC in "// appease MSC" comments mean? -

javascript - Blogger related post gadget image Resize s72-c [ Need Expert Help ] -