# Qualys Security Verification

**URL:** <https://community.auth0.com/t/qualys-security-verification/187288>\
**Category:** Dev to Dev Hub\
**Tags:** security-compliance, security-question-concern\
**Created:** [May 28, 2025, 1:40pm UTC](https://community.auth0.com/t/qualys-security-verification/187288 "2025-05-28T13:40:36Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![murilo.gomes](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/murilo.gomes/32/75026_2.png) [@murilo.gomes](https://community.auth0.com/u/murilo.gomes)\
**Post date:** [May 28, 2025, 1:40pm UTC](https://community.auth0.com/t/qualys-security-verification/187288/1 "2025-05-28T13:40:36Z")

</div>

Hi guys,

We started testing Auth0 in our application to provide more security and reliability to our customers. However, one of these customers applied the _Qualys TotalAppSec_ security verification test and identified a medium vulnerability and two info security weaknesses. The customer wants this vulnerability and the two info security weaknesses to be resolved, so I kindly ask for the community’s help so that we can resolve these issues.

**Vulnerability:**

- 150476 Cookies Issued Without User Consent, we tried to resolve it by applying this possible solution - [link](https://community.auth0.com/t/cookies-issued-without-user-consent/113769). Would that be the only one or would there be something else to be done?

**Info Security Weaknesses:**

- Third-party Cookies Collected: The refresh token was configured, but the custom domain was not yet configured. Would this problem be resolved with the refresh token and custom domain or would there be something else to be done?

- Cookie without SameSite attribute: in this topic, I honestly don’t know how to solve it. I saw this [link](https://auth0.com/docs/manage-users/cookies/samesite-cookie-attribute-changes) and didn’t see how to solve it. Can anyone point out a solution or even an article that invalidates this point? One solution that could solve this would be to assign the cookie as strict, but I believe I do not have access to such settings.

Thanks

---

<div class="post-metadata">

**Author:** ![murilo.gomes](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/murilo.gomes/32/75026_2.png) [@murilo.gomes](https://community.auth0.com/u/murilo.gomes)\
**Post date:** [May 28, 2025, 4:58pm UTC](https://community.auth0.com/t/qualys-security-verification/187288/2 "2025-05-28T16:58:33Z")

</div>

Guys, about vulnerability 150476 Cookies Issued Without User Consent, have more detail: The cookies listed in the Results section were issued from the web application during the crawl without accepting any opt-in dialogs.
