1 |
pappy 07/10/27 21:30:01 |
2 |
|
3 |
Added: index.xml |
4 |
Log: |
5 |
adding preliminary version of project homepage |
6 |
|
7 |
Revision Changes Path |
8 |
1.1 xml/htdocs/proj/en/extreme-security/solutions/index.xml |
9 |
|
10 |
file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/proj/en/extreme-security/solutions/index.xml?rev=1.1&view=markup |
11 |
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/proj/en/extreme-security/solutions/index.xml?rev=1.1&content-type=text/plain |
12 |
|
13 |
Index: index.xml |
14 |
=================================================================== |
15 |
<?xml version='1.0' encoding="UTF-8"?> |
16 |
<!DOCTYPE guide SYSTEM "/dtd/guide.dtd"> |
17 |
|
18 |
<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/proj/en/extreme-security/solutions/index.xml,v 1.1 2007/10/27 21:30:01 pappy Exp $ --> |
19 |
|
20 |
<guide link="/proj/en/extreme-security/solutions/index.xml"> |
21 |
<title>Security Solutions</title> |
22 |
<author title="Author"> |
23 |
<mail link="pappy@g.o">Alexander Gabert</mail> |
24 |
</author> |
25 |
|
26 |
<!-- |
27 |
<author title="Contributor"> |
28 |
<mail link="XXX">YYY</mail> |
29 |
</author> |
30 |
<author title="Editor"> |
31 |
<mail link="XXX">YYY</mail> |
32 |
</author> |
33 |
--> |
34 |
|
35 |
<abstract> |
36 |
|
37 |
|
38 |
The technology and tools used to realize a security policy |
39 |
will be the answer to the attack vectors determined by an |
40 |
accurate threat model with the appropriate financial backup of the business model. |
41 |
|
42 |
|
43 |
</abstract> |
44 |
<version>0.1</version> |
45 |
<date>2007-10-27</date> |
46 |
|
47 |
<chapter> |
48 |
<title> |
49 |
|
50 |
|
51 |
|
52 |
</title> |
53 |
<section> |
54 |
<body> |
55 |
<p> |
56 |
</p> |
57 |
<p> |
58 |
</p> |
59 |
<p> |
60 |
</p> |
61 |
|
62 |
<note> |
63 |
|
64 |
<!-- |
65 |
|
66 |
TODO |
67 |
|
68 |
solutions: design a backup solution |
69 |
- written backup/restore/rebuild policy |
70 |
|
71 |
solutions: design a security solution (layered approach) |
72 |
- written security policy |
73 |
- the role of the IT security principal |
74 |
- physical site security |
75 |
- network security |
76 |
- firewalls |
77 |
- proxies |
78 |
- network intrusion detection systems |
79 |
- honeypots |
80 |
- loghosts |
81 |
- demilitarized zones |
82 |
|
83 |
- operating system security |
84 |
- password security |
85 |
|
86 |
- update policy |
87 |
- security review policy |
88 |
- penetration testing (portscans vulnerability scans) |
89 |
- trusted path execution |
90 |
- role based access control |
91 |
- chroots, virtual servers, virtualization |
92 |
- filesystem monitoring, filesystem integrity checking |
93 |
- remote logging |
94 |
|
95 |
- application level security |
96 |
- intrusion detection |
97 |
- forensic support |
98 |
|
99 |
- introduce webgoat for web applications |
100 |
- introduce Payment Card Industry Security compliance as a model for successful IT security audits |
101 |
|
102 |
--> |
103 |
</note> |
104 |
</body> |
105 |
</section> |
106 |
</chapter> |
107 |
|
108 |
|
109 |
</guide> |
110 |
|
111 |
|
112 |
|
113 |
-- |
114 |
gentoo-commits@g.o mailing list |