Four papers are:
Thursday, August 11, 2011
Weekly Summary 08/01~08/11
Four papers are:
Monday, August 8, 2011
Game Theory meets Network Security and CPS
Thursday, July 28, 2011
Summary: Case study (experiments) related to intrusion response, security analysis
Tuesday, July 26, 2011
security analysis using Fault Trees (FT)
Wednesday, July 20, 2011
some existing intrusion response system
Tuesday, July 19, 2011
quantitatively measure the performance, dependability, perfomability and security
Monday, July 18, 2011
prospective research
Wednesday, July 13, 2011
Intrusion response and recovery
Tuesday, June 14, 2011
Control techniques in NCS
Paper Reading: Control methodologies in networked control systems
After reading paper “Simulation of Network Attacks on SCADA system”, I was thinking maybe I could do a series of simulation to analyze the effects of network attacks on NCS. Different from previous work, I was thinking to make two situations, one with full-fledged DoS attack on routers so that the network will be essentially broken at that point and result in a loss of regulatory function of the controller, complete loss of the communication between controller and plant; the other with only attacking some factors inside plant, not the whole plant, so that the controller is not blind to any of the required sensors, but its regulation function could be still hampered by it not being able to control all the factors in the plant. This requires a deep understanding on the NCS we are using in NCSWT. This is the idea coming from control perspective. Maybe I could make some change to the NCS to output some more factors or let it have some more input values besides x, y, id we already had. This is why I read thoroughly over control technique.
Some valued points got from this paper:
In the NCS research field, regardless of the type of network used, the overall NCS performance is always affected by network delays. This network delay (time-varying, constant, periodic) still significantly affects the close-loop system. And it requires an advanced control methodology. (Before that, I was thinking with the development of network today, network speed, network bandwidth is making this delay almost ignorable. It may not be necessary to make network delay as research object since it may not have a significant effect on NCS performance. I was wrong.)
This network delay is composed of sensor-to-controller delay and controller-to-actuator delay for all the NCS, including hierarchical structure (multiple control system with one or multiple main controller).
To be noted that, for the effects of delays in the close-loop control system, it only has two main effects. One is widely known to degrade system performances of a control system, such as higher overshoot and the longer settling time when the delays are longer than expected. The other one is to destabilize the system by reducing the system stability margin. There have been several studies to derive stability criteria for an NCS in order to guarantee that the NCS can remain stable in a certain condition. However, there is no generic stability analysis that can be applied on every NCS. I guess this could still use the frequency domain analysis for checking stability when the delays are added into the system.
For the control techniques used to solve this network delay problem, you have to maintain the stability of the system first and then try to maintain the performance of the system. Two methods were caught into the eyes:
Sampling time scheduling methodology, to appropriately select a sampling period for an NCS such that network delays do not significantly affect the control system performance;
Event based methodology, instead of using time, this method uses a system motion as the reference of the system.
To be continued…
Wednesday, June 1, 2011
Paper Reading on: Modeling Load Redistribution Attacks in Power Systems
Thursday, March 24, 2011
ToDo threat model in NCSWT
Thanks for these days work with newer version NCSWT. I'm now much familiar with C2WT.
We know the security goal that NCS should achieve lies in the order of importance, availability, integrity and confidentiality. How to select the appropriate security mechanisms requires a threat model first.
Threat taxonomy:
We could categorize the attacks into three main types:
1. outsider attacks. (This is where we focus)
--Deception attack (spoofing attack)
Using new version NCSWT, we could now easily change the values transmited between controller and plant by spoofed packets, causing it to perform undesired effects. I was thinking maybe could do several kinds of spoofing here. Try to find some more information. The analysis could be done offline by data from control system.
--Denial of Service attack (jamming attack)
Jamming is the interference with the Radio Frequency(RF) used by the nodes in a network. It makes use of the broadcast nature of the communication medium. We don't want to compromise the availability of network, just need to give the control network some more delay. Because if there is no network availability we can easily notice the attack and take some correct actions. There is no need to detect. I think it is meaningful that if we could detect out that there is a lot of traffic in the network and then launch an alarm. This could be done in the ns2, online. In simulation system, this kind of work has not been done before.
--Replay attack
In a replay attack, a transmitted packet is maliciously or fraudulently repeated or delayed by the adversary. I have an idea that this could also be done in NCSWT, by revising some code in ns2.
2. Key-compromise attacks.
Since low-entropy of certain measurement reports, confidentiality could be easily compromised by simple traffic analysis. So, most systems use encryption to ensure confidentiality. However, this secret key may be stole or compromised by adversary. We may not do this, since we don't do encryption in the first place.
3. Insider attacks.
adversary act as legitimate nodes in the network.
Saturday, February 19, 2011
whole background with security problem over CPS
from plant or controller. the false information could include: an incorrect measurement, the incorrect time when the measurement was observed, or the incorrect sender id. The adversary can launch these attack by compromising some sensors or controllers. I will try to realize it in ns2. Capture the package and then revise the data inside.