search

OWASP / ASVS

Application Security Verification Standard
Creative Commons Attribution Share Alike 4.0 International
2.71k stars 662 forks source link

Updated Excel Sheet for ASVS! #1318

Open deFr0ggy opened 2 years ago

deFr0ggy commented 2 years ago

I just worked onto updating the CSV format specifically for the people who make extensive use of EXCEL. Beautified it a little so its easy for the eyes to keep up. Plus removed the columns which were not required.

Screenshot and updated file attached!

Issue 1

Removed Chapter Name Column

Issue 2

Level Issue

Updated Excel

OWASP.Application.Security.Verification.Standard.4.0.3-en.csv

Updated Excel Screenshot

Updated Excel

Will work on it a little more later on to build up a dashboard for tracking and reporting!

Thank you!

elarlang commented 2 years ago

As we generate those files automatically, we are not going to change them with manually edited ones.

If you have clear proposals for "Makefile guys", what are the expected changes, then it's maybe automatically generated in the future.

tghosth commented 2 years ago

Hi @deFr0ggy,

As Elar said, we tend to restrict our outputs to those which are automatically generated.

However, if you fancy looking at the python files in this folder and figuring out why we have those weird characters you highlight in "issue 2" above, that would help a lot :)

deFr0ggy commented 2 years ago

The issue seems to be with MS Excel as by default it does not detects the Unicode Characters. In order for it to read file correctly, we need to load the file in the following manner.

DATA -> From Text/CSV -> Change The Origin (1252: Western European to 65001: Unicode (UTF-8)

Will check if we can have this fixed somehow using the python script!

tghosth commented 2 years ago

It is definitely a python problem as it is already exported like that into the CSV text file

deFr0ggy commented 2 years ago

Yes, the file is being exported in UTF-8 format although the default format of MS Excel is not same which causes rendering of UTF-8 characters into other ones!

tghosth commented 2 years ago

My sincere apologies, I mis-spoke above. It actually looks correct in a text editor so it is just in Excel where it looks weird so I am open to suggestions if there is a way to export in a text encoding format that will work immediately better in Excel.

ike commented 8 months ago

I would suggest we use a converter to xlsx, there are a lot of problems getting Excel data types and unicode support from a CSV without also sacrificing the usability of the CSV in other automated settings.

This is a small binary converter we could use in the document builder which supports column data types, unicode, date conversions, etc.

tghosth commented 8 months ago

Happy to see a PoC :)