Intrusion tolerant architecture for SDN networks through flow monitoring

被引:0
作者
Manu, B. [1 ]
Koundinya, Anjan K. [1 ]
机构
[1] RV Coll Engn, Dept Comp Sci, Bangalore, Karnataka, India
来源
2017 2ND INTERNATIONAL CONFERENCE ON COMPUTATIONAL SYSTEMS AND INFORMATION TECHNOLOGY FOR SUSTAINABLE SOLUTION (CSITSS-2017) | 2017年
关键词
SDN; Intrusion tolerant Architecture; Opendaylight;
D O I
暂无
中图分类号
TP39 [计算机的应用];
学科分类号
081203 ; 0835 ;
摘要
Security is of paramount importance to any system to function without disruptions of any kind. But protection of the underlying infrastructure from the diverse types of attacks is not easy to tackle. While complete protection is still a distant reality, the notion of tolerance to intrusion is a compelling concept. In intrusion tolerant architectures, instead of trying to prevent every single intrusion, these are allowed but tolerated. The system has the means to trigger mechanisms that prevent the intrusion from generating a system failure. There are a lot of papers in classical IP-based networks regarding intrusion tolerant system but a very few introduce the concept of intrusion tolerance in software define networks(SDN). Software-defined networks (SDN) is an emerging architecture that detach control plane from the data plane. SDN control plane consists of controller which can control the entire network. This centralized view of the network with the ability to program the network through external applications can be used for developing intrusion tolerant architecture. In this proposed architecture, Intrusion Detection Module needs to be developed in the Opendaylight SDN controller. It monitors the packet count for flows. The packet rate is calculated by requesting flow statistics from the switch and monitoring packet counts at different intervals. If the rate exceeds the threshold value, a higher priority flow with the same match criteria is added with action as punt to controller. This flow will have an idle timeout of 5secs which prevents overburdening of sending a lot of packets to controller. The next few packets are thus punted to controller. Controller will perform deep packet inspection and if the packet is from a known sender, then appropriate rate limiting is done at the beginning of the pipeline. Else if the packet is from an unknown source, a new flow is added with relevant match details and an action of drop is added. This will drop all the packets sent from the unknown sender and thereby protecting the system from failure
引用
收藏
页码:284 / 288
页数:5
相关论文
共 8 条
[1]  
[Anonymous], 2014, Proceedings of the IEEE International Symposium on a World of Wireless, Mobile and Multimedia Networks WoWMoM, DOI DOI 10.1109/WOWMOM.2014.6918979
[2]  
Blog. packet- foo. com, 2017, TCP AN 5 TUPL PACK F
[3]  
Chen PJ, 2015, INT CARN CONF SECU, P141, DOI 10.1109/CCST.2015.7389672
[4]  
Ibrahim Juma, 2017, 2017 INFOTEH JAHORIN, P2
[5]  
Jankowski Damian, 2015, 2015 J TELECOMMUNICA, P7
[6]  
OpenDaylight, 2017, HOM OPENDAYLIGHT
[7]  
Sayeed MA, 2015, 2015 1ST INTERNATIONAL CONFERENCE ON NEXT GENERATION COMPUTING TECHNOLOGIES (NGCT), P379, DOI 10.1109/NGCT.2015.7375145
[8]  
Xing TY, 2014, INT CONF NETW SER, P308, DOI 10.1109/CNSM.2014.7014181