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 at
spsmm<at>isecom.org.
Download the SPSMM in pdf or LaTeX:
| Size
Date Time Name
|
Spain |
USA |
| 15400 Dec 1 2002
spsmm-description.en.v0.5.1.tex.gz... |
 |
|
| 144004
Dec 1 2002 spsmm.0.5.1.en.pdf................... |
|
|
| 153224
Dec 1 2002 spsmm.0.5.1.es.pdf................... |
|
|
| 480440
Dec 1 2002 spsmm.0.5.1.jp.pdf................... |
|
|
| 247627
Mar 18 21:00 spsmm.0.5.1.pt.pdf................... |
|
|
Japanese translation of
the "SPSMM-セキュアプログラミング標準化手法マニュアル"
by
Ikeda Masakazu
Portugese translation of the SPSMM
by Sandro Melo
TEAM ACCESS