 |
 |
| The description of dCERT services given here
is according to RFC2350. RFC2350 "Expectations for Computer Security
Incident Response" contains the possible activities of a CERT and
recommends a selfdescription, whose sample we are following. |
| |
 Document
Information
 Contact
Information
 Charter
 Policies
 Services
 Incident
Reporting
 Disclaimers
|
| |
 |
| |
1. Document Information
1.1 Date of last update
Version 1.0.5, published 2005-05-11.
1.2 Distribution list for notifications
Notifications of updates are submitted to our customers using mailinglist
and forum.
1.3 Locations where this document may be found
The current version of this dCERT description document is available
from the dCERT Website http://www.dcert.de/mission.html.
An english version can be obtained from http://www.dcert.de/mission_e.html.
Please make sure you are using the latest version.
1.4 Authenticating this document
Integrity and authenticity of electronic documents can be achieved
by using digital signatures (see 2.8). Both the german and the english
version of this document have been signed with the dCERT's public
key. Signed version of this document are available on request. |
|
|
 |
| |
2. Contact Information
2.1 Name
"dCERT" Computer Emergency Response Team.
2.2 Address
dCERT
T-Systems
ICT Operations
Vorgebirgsstr. 49
53119 Bonn
Germany
2.3 Time Zone
Europa/Berlin (GMT+0100, and GMT+0200 from April to October)
2.4 Telefon
+49 (228) 9841-5500
dCERT customers and FIRST members (on request) are given an emergency
phone number, by which dCERT can be reached in case of emergency (FIRST
= Forum of Incident Response and Security Teams).
2.5 Facsimile Number
+49 (228) 9841-6000 (not a secure fax)
2.6 Forum
dcert customers and FIRST members (on request) are invited to discuss
all security-related problems using a moderated discussion forum.
2.7 Electronic-Mail address

(The address forwards to all dCERT-employees.)
2.8 Public Keys und Vertraulichkeit
dCERT unterstützt die signierte und vertrauliche Kommunikation
nach den Standards von MailTrust, S/MIME und PGP.
2.8.1 PGP-Key
-----BEGIN PGP PUBLIC KEY BLOCK-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: dCERT by T-Systems ISS GmbH
mQGiBDxRiPYRBACpTheYq2cOWticUyKI3Pao5memxGt
BjybPT65WJqNVh5mQW+b90qnEbJuSj/Sfu7d1/vD1cp
0FXRwuT+Ca7TKF5qz/UvHPReVUJ18nfzEoZmMUg1yMD
4m4HYwPAlQ+HnmBHTAf5BBFmKL8GjdcbuRIpfENBCF1
7nJH7dFKNwVm1wCgmfPlrTFay04YbVkJTQ1xdALvMRk
D/34QFNu1gNqq9Ur8Sq2NCxw8yp1K4V/Uhf2MW6yMeA
Mdo2O/D2H/WKPE9znGXsPl3wcYGxygP+hF7x/UpKZee
RLswW0nVt/hIZ3HlVBYWIgp39QtDog0C6Lzs8fto+H5
zx6RpyYr1XlP40Yf7FnARJ1a7HyVi3CXx/LDBROIWvt
UA/sHrxCeeIsIHIsPv7DKagF8lJCob45ZyzNZkErEp4
4IxAiQqPw2CJZkka+bdI0aK40wc7oB3M54RLQf1mzf5
M4xsx/kaD3JngnhUQkOU+7DMcydEA8KxJR5dCNFccS6
erYOOoQ6/ff3ffbgrmOSwWpRymoq7nLXmnrRfWGx1NR
zq7QtZENFUlQgKGFkdmlzb3J5IHNpZ25pbmcga2V5KS
A8ZGNlcnRAZGNlcnQuZGU+iFcEExECABcFAjxRiPYFC
wcKAwQDFQMCAxYCAQIXgAAKCRD5KSLC34f0KhY5AKCN
DXPt5LuXBsil4GqbH7V7Le9NWgCfQ9UestJdUG4wLp0
p6omLPsu+qZ2InAQQAQEABgUCPFFu/QAKCRATb7l7pg
s8/x3ZA/9Me/1TG+nlzRA+Rcz7uCKsMs93FGZ//cv2W
3TbijatL7FEy2W7OlbkF62uL8BhbIlMZKXbrci4iSlL
A8E1gaEjJvY/DpBsHeMhlV58i1NVlVJ2xlLKY8FMN3R
RtttM8FWmLm+yCPIY/tqPpTgSotttxUpivefaKkr+NZ
G0qsv+5okBHAQQAQEABgUCPFFvwQAKCRCdPLuWz3STN
d3GCADGL2epqTHsyrumnSwIQ/KAjxPE1B/1rz++T9W4
+iVz2fwoxVU357ehvkFfYIC2wtspMHyf1VwatCBEH01
SgxU4OXP7aF4TCjZfUdgFVuib6uQxZq23Pz8vAcooqf
3HuosAWzb6WNe1KlxHYvyNHThctHvaUslZuNAL/O2co
5EhHGNYJytofiLAQRlW+OVi6wbMy9Y+Dr4zqvwz4g1Z
d99bBphVEwjDEFNO5Dbz3BKT2P6FsHLruYep21C1W4D
x1UkSOfrt3EjyM+3fJutoiixGrAYlmFJzLySK50jKbp
vrJFmzGAJPxgSq3OeHH0MTTZxxTDv+23ifrQQWjf4Rf
0fouQENBDxRiP8QBACXhGZVWGGDkq/7Y8Zx7Rv1U3j6
p3gPw3EDmFFxBK6JMfpLCzqnmqmoJUPpU/ZWSDP8Ubv
hsY1ZifPnscpmh47ts2a/9Nwz7+le8qegD7x+c3VilO
XixC6i8peAG3MN6gtHlvx+z/FQs7iAArMaqvQ8yrJIK
AtROr2n4w3GSWInfwADBwQAjRiLdHN4q0/3941WfaDM
+h//LfA6OrUBaeN52Cqhgpj1Hy7dHRtwz76lJectyHl
osJFx3lKsyX92Av7+iBduF+kQDQq2ahZ+YfK/VMCF8G
LcRkDdt1vjrV200TtK72MwWmJFa8iN6UjgdjAIKuM9/
5cpg8Qh2wPVSEzlQQRVnIeIRgQYEQIABgUCPFGI/wAK
CRD5KSLC34f0KuScAJwLmL+zhhRmXS8zl7r+CcXm0SE
81QCdFKHVPCM64SO4iYknYB92AsTp0K8==j125
-----END PGP PUBLIC KEY BLOCK-----
2.9 Team Members
dCERT is organised by highly qualified employees of T-Systems who
mainly work in the department of "Secure Systems" and "Communication
Security". The complete portfolio of T-Systems can be seen at
http://www.t-systems.com/ict-security.
Customers may receive more detailed employee profiles on demand.
All members of dCERT are security examinated by the minister of economics
and are allowed to access documents up to confidentiality level "GEHEIM".
2.10 Other Information
General information about the dCERT can be found at http://www.dcert.de/.
2.11 Points of Customer Contact
dCERT can be reached using e-mail (2.7), fax (2.5), forum (2.6) and
phone (2.4). dCERT prefers electronic communication.
dCERT's working hours are Monday to Friday 9:00 to 18:00 except holiday.
In case of emergency dCERT can be contacted by customers the remaining
days as well. |
|
|
 |
| |
3. Charter
3.1 Mission
Primäres Ziel des dCERT ist die proaktive Versorgung seiner Kunden
mit aktuellen Informationen zu neuen Schwachstellen in der IT-Sicherheit
und deren Abhilfen. Bei Eintritt sicherheitsrelevanter Vorfälle
bietet dCERT Hilfe und Unterstützung.
3.2 Constituency
dCERT works exclusively for its customers.
3.3 Affiliation
dCERT belongs to T-Systems http://www.t-systems.com/,
Germany's largest and vendor-independent IT-services company.
3.4 Authority
dCERT realizes proactive services as described in 5.1. All further
activities by dCERT are solely initiated on request of the customer.
|
|
|
 |
| |
4. Policies
4.1 Types of incidents and level of support
dCERT offers help and support to address all types of information
security incidents which occur at the customers' sites. The amount
of support is determined by the customer.
The proactive services of dCERT are primarily focused to security
officers and security administrators.
4.2 Co-operation, interaction and disclosure of information
In principal, dCERT will treat all customer-related information as
high confidential. dCERT treats all personal information in accordance
with the german data protection act. dCERT will share information
only with the customer's agreement. dCERT may share anonymised non-customer-related
information with other FIRST members when this will assist others
in resolving or preventing further incidents.
4.3 Communication and Authentication
Non-sensitive information will be sent using ordinary e-mail. Confidential
information will mainly be sent encrypted using e-mail. Phone and
fax will be used without special precautions.
Every customer has to name a contact person. The contact person authorises
further employees at the customer on demand. |
|
|
 |
| |
5. Services
5.1 Proactive Activities
dCERT supports the IT security measures of its customers in manifold
ways and an up-to-date manner.
5.1.1 Mailinglist
Information for basic security of applications, computers and networks
will be daily analysed, evaluated and distributed along with countermeasures
electronically per e-mail. Digests are published once per month.
5.1.2 WWW-Server
All distributed information are permanently stored on the WWW-server
http://www.dcert.de/ and can be searched.
5.1.3 Forum
dCERT partners can join the moderated forum http://www.dcert.de/customer/forum.html
in order to exchange experiences and to discuss with experts of T-Systems.
5.1.4 Analystentage
Monatlich einmal kann der Austausch individuell zu allen Themen der
IT-Sicherheit vertieft werden.
5.1.5 Security Seminars
Selected topics of IT-security both as an overview and in depth are
the subject of annual security seminars.
5.2 Incident Response
dCERT is prepared to assist customers in handling the technical and
organisational aspects of security-related incidents.
5.2.1 Incident Triage
dCERT is prepared to assist customers in handling the technical and
organisational aspects of security-related incidents.
5.2.2 Incident Coordination
Customers will be supported in order to react internally and externally
in an adequate way. dCERT will notify further sites which may be involved,
FIRST-members and public institutions on behalf of the customer and
in a neutral way.
5.2.3 Incident Resolution
Countermeasures which resolve or work around the used leaks and loopholes
are of first priority. Taking of evidence and further activities are
done on customer's demand. |
|
|
 |
| |
6. Incident Reporting
Forms
Up to the finishment of dCERT's incident reporting form please make
use of the "Incident Reporting Form" of the CERT Coordination
Center (Pittsburgh, PA)
http://www.cert.org/reporting/incident_form.txt . |
|
|
 |
| |
7. Disclaimers
The information distributed by dCERT has been obtained from sources
believed to be reliable and trusted or have been verified. T-Systems
can take liability for completeness, accuracy and correctness only
in so far, as gross negligence or intention create liability. Any
liability beyond it, in particular possible damages resulting from
using or non-usability of the information contained herein, is excluded.
|
|
|