Incident Report X040705 |
|
A running diary and job jar on Incident X040703
Status |
Date |
Description |
2004-08-27 | Say why this is an incident instead of a project and maybe make a project too. | |
2004-08-27 | Using the Threat Modeling Tool and its use of Data Flow Diagrams might be a slick way to do this. There is material I have from my Information Security Engineering course that I should be able to apply here too. | |
2004-07-31 | Include the Infra-red port on Compagno as another attack point | |
done | 2004-07-28 | Get the Gibson buttons that are linked to that site, so they can be resolved locally |
2004-07-28 | Identify intranet attack surface and how well it is blocked | |
2004-07-28 | Do an isolation of the DSL Modem and see what it does not block from external senders | |
2004-07-28 | Do an assessment of ZAPro in terms of countermeasures it provides and how they are useful here. Identify unconfirmed trust points. This will lead to identification of other components that also must have confirmed trust. | |
done | 2004-07-28 | Start a simple attack-surface overview that identifies the external attack points and the internal ones. |
done | 2004-07-28 | Coalesce Gibson Research analysis from 2004-07-27 into a simple summary |
done | 2004-07-28 | Create Visio and PNG Diagrams of the attack surface from Compagno perspective |
done | 2004-07-28 | Start the incident report with basic information and an outline |
You are navigating Orcmid's Lair |
created 2004-07-28-13:01 -0700 (pdt) by orcmid |