I recently discovered the project SATEC. I would like to proposed few
modifications to the document.
Expanding "Tool Coverage" (section 3)
Few sub-sections should be added.
(include simply for distinction with the following)
(3.4 -"... Understand components" could be reformulate to Configurations)
Product Update Process * (section 7)*
On my first read, I thought the section 7 (which end up in section 4 on the
first draft) was not appropriate to the Code analysis context .
Static code analysis is very different from malware analysis. Every new
binaries in malware analysis is likely to have been
In development, the framework and languages used do not evolve rapidly.
From time to time, libraries are introduce to support new functionalities.
But there are no 0 day API. ;)
I'm not trying to demolish the previous work. I think the criteria list was
That's it .. I hope I'll be able to collaborate on the project.
The second draft actually include few things I mentions (Framework and
rename to Configuration). At first, I did not red the proper document.
Nonetheless, I think library should be mentions.
Any thought about the necessity for signature update ?