 |
| |
 |
|
|
|
|
SPSMM - The Secure Programming Standards Methodology Manual
by
Victor A. Rodriguez (Bit-Man)
When you expose an
interface ( programming, user, etc.) it can be used or abused. It is abuse
that should be avoided (depending on what side of the coin you are). Since we
plan to standardize this methodology from the programming side and as so you
may be a programmer, system architect, team leader, etc. you want to keep your
interface clean, usable, and with no component capable of being abused.
As Internet applications get more and more complex and the human element
becomes less involved in the interface (both bad and good) we are at a
distinct disadvantage when you play the odds. Techniques for secure
programming is something that has been tackled in many forms and for many
languages. We are attempting to meet this with a single methodology regardless
of programming language and application environment.
If you are interested
in helping with this project please
contact us.
Download the SPSMM in pdf or
LaTeX:
| Name
|
Spain Mirror
sponsored by |
USA Mirror
sponsored by
|
|
spsmm-description.en.v0.5.1.tex.gz |
 |
 |
|
spsmm.0.5.1.en.pdf................ |
 |
 |
|
spsmm.0.5.1.es.pdf................ |
 |
 |
|
spsmm.0.5.1.jp.pdf................ |
 |
 |
|
spsmm.0.5.1.pt.pdf................ |
 |
 |
Japanese translation of
the "SPSMM-セキュアプログラミング標準化手法マニュアル"
by
Ikeda Masakazu
Portugese translation of the SPSMM
by Sandro Melo
|


|
ISECOM is an open, collaborative,
non-profit, scientific, security research organization registered in Catalunya, Spain. All research here has been performed without
commercial or partisan influence. Contact
us directly to be a security researcher on the ISECOM team.
 |
|
Disclaimer:
While all documents on this site are available under
Copyleft and the
Open Methodology License,
do check the licenses within each tool or document prior to copying,
modifying, or distribution for any individually stated requirements.
Additionally, all research is provided here for information purposes
only and ISECOM is not responsible for any misuse. |
|
|
|