![]() |
![]() |
|
| A project co-funded by EU FP6 programme |
|
Recommendation: |
| |||||||||||||||||
| What: | The information about which resource is administered by whom should be stored in a central database and its consistency has to be regularly checked. Ideally it will be connected with an Identity Management System to ensure that resources from leaving personnel are reassigned to avoid unattended machines. | ||||||||||||||||||
| Why: | During a security incident it is important to identify the responsible person for a compromised resource as fast as possible in order to react. A central database connecting each resource to a responsible person (administrator) helps identify the right person to respond appropriately and avoid further damage. | ||||||||||||||||||
| How : |
Connect existing databases to interlink resources to the people responsible for them
Often the different responsibilities of one person are stored in a distributed way over several existing databases. To avoid data inconsistency and to allow the security officer to react fast to security incidents it is important to merge the different resources or at least to offer access to all information via a single front end.
Hints: Links: |
||||||||||||||||||
| Relevant recommendations | |||||||||||||||||||
| Relevant threats: | |||||||||||||||||||
| Relevant ISS audit questions: | |||||||||||||||||||
| Keywords |
Incident, Sensitive, Device, Developer, System, Administrator, Intrusion, Detection, Desktop, Worm, Virus, Management, Policy |
||||||||||||||||||
| Recommendation Category: |
|
|
Copyright (c) Members of the ISSeG Collaboration 2008 |
Top of page | Home page |
|
|
This is version 5.2 of the website - view release notes -view visitor statistics |
|||