Intrusion-Tolerant Middleware
The Road to Automatic Security
The pervasive interconnection of systems throughout the world has given computer service a significant socioeconomic value that both accidental faults and malicious activity can affect. The classical approach to security has mostly consisted of trying to prevent bad things from happening---by developing systems without vulnerabilities, for example, or by detecting attacks and intrusions and deploying ad hoc countermeasures before any part of the system is damaged. But what if we could address both faults and attacks in a seamless manner, through a common approach to security and dependability? This is the proposal of intrusion tolerance, which assumes that
Systems remain somewhat faulty or vulnerable;
Attacks on components will sometimes be successful; and
Automatic mechanisms ensure that the overall system nevertheless remains secure and operational.
The Road to Automatic Security
The pervasive interconnection of systems throughout the world has given computer service a significant socioeconomic value that both accidental faults and malicious activity can affect. The classical approach to security has mostly consisted of trying to prevent bad things from happening---by developing systems without vulnerabilities, for example, or by detecting attacks and intrusions and deploying ad hoc countermeasures before any part of the system is damaged. But what if we could address both faults and attacks in a seamless manner, through a common approach to security and dependability? This is the proposal of intrusion tolerance, which assumes that
Systems remain somewhat faulty or vulnerable;
Attacks on components will sometimes be successful; and
Automatic mechanisms ensure that the overall system nevertheless remains secure and operational.
쉼터에 새로운 글 쓰기는 금지되었습니다. 하지만 과거의 소중한 기록 중에 꼭 다른 분들에게도 읽었으면 하는 좋은 글들은 「추천하기」를 눌러주세요.
일부 글들은 악성광고나 의미없는 스팸들일 수 있습니다. 읽는 분들에게 피해가 되거나 삭제를 희망하는 글에는 신고를 클릭해주세요. 로봇을 통하여 정기적으로 확인 및 정리를 합니다.