HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
OWASP
ASVS
HTML2015–2025
OWASP / ASVS

ASVS

Application Security Verification Standard

Security & Privacy
Explore on GitHubRead Hacker News discussions
7Distinct people
10Mentions
0Explicit recommenders
3.8KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

Application Security Verification Standard

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 8–Nov 15 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/15/2026, 10:56:20 AM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by year10 dated mentions

Observed mentions: 2015-07-03 16:28:35 UTC to 2025-10-22 19:49:40 UTC.

0122015-01-01 00:00:00 UTC to 2016-01-01 00:00:00 UTC (exclusive): 2 mentions; 1 submissions, 1 comments20152016-01-01 00:00:00 UTC to 2017-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2017-01-01 00:00:00 UTC to 2018-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2018-01-01 00:00:00 UTC to 2019-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2019-01-01 00:00:00 UTC to 2020-01-01 00:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 comments2020-01-01 00:00:00 UTC to 2021-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments20202021-01-01 00:00:00 UTC to 2022-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2022-01-01 00:00:00 UTC to 2023-01-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments2023-01-01 00:00:00 UTC to 2024-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2024-01-01 00:00:00 UTC to 2025-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2025-01-01 00:00:00 UTC to 2026-01-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments2025

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
20152015-01-01 00:00:00 UTC2016-01-01 00:00:00 UTC211
20162016-01-01 00:00:00 UTC2017-01-01 00:00:00 UTC000
20172017-01-01 00:00:00 UTC2018-01-01 00:00:00 UTC000
20182018-01-01 00:00:00 UTC2019-01-01 00:00:00 UTC000
20192019-01-01 00:00:00 UTC2020-01-01 00:00:00 UTC110
20202020-01-01 00:00:00 UTC2021-01-01 00:00:00 UTC000
20212021-01-01 00:00:00 UTC2022-01-01 00:00:00 UTC101
20222022-01-01 00:00:00 UTC2023-01-01 00:00:00 UTC202
20232023-01-01 00:00:00 UTC2024-01-01 00:00:00 UTC101
20242024-01-01 00:00:00 UTC2025-01-01 00:00:00 UTC101
20252025-01-01 00:00:00 UTC2026-01-01 00:00:00 UTC202

What Hacker News says

1 sources
linsomniac·Aug 9, 2019Submission

Ask HN: How do you “verify” app security?

We are currently going through the OWASP "Application Security Verification Standard" ( https://github.com/OWASP/ASVS ) to increase security of an existing web app. Many of the items in that checklist are "verify X". To me, when it says "Verify requests to uploaded files will never be executed as HTML/JavaScript", that means spend hours visiting every place where files may be uploaded, find the corresponding download, and check the code to make sure it won't be interpreted as HTML/JS. There are 132 items just in the "L1" part of the standard (the minimum recommended protections), which seems like it could be thousands of hours to "verify" all of those. But the OWASP ASVS says that half the things in L1 are probably automatically testable or testable in the CI/CD pipeline. Clearly we don't want to manually verify all these things, as that
Read the rest
doesn't prevent drift as time goes on. But we also don't have a process that would automate any of this. It seems like having access to request logs would allow us to identify many things (like whether API tokens are exposed in URLs) and access to live production data streams as they go through the load balancer would allow us to detect file uploads and content types sent back. But I'm unaware of tools for doing that. Cloudflare has their "web application firewall", which probably helps some with this on an ongoing basis, I think that starts at $5K/month. AWS has a WAF as well, and you can purchase subscriptions to rules for checking traffic, and some of those mention OWASP. Right now we are going over OWASP doing some "gut feel" what items are the highest priority and are likely to be vulnerable to. We've also been looking at code and finding some definite security issues. But longer term we need to present to non-technical board members why we aren't scanning all file uploads with A/V software, for example. Anyone have any wisdom on how you are "verifying" compliance with security standards?
1 points · Open discussion

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.