2014
DOI: 10.1109/jsac.2014.2358817
|View full text |Cite
|
Sign up to set email alerts
|

High-Speed Application Protocol Parsing and Extraction for Deep Flow Inspection

Abstract: In this paper, we propose FlowSifter, a framework for automated online application protocol field extraction. FlowSifter is based on a new grammar model called Counting Regular Grammars (CRG) and a corresponding automata model called Counting Automata (CA). The CRG and CA models add counters with update functions and transition guards to regular grammars and finite state automata. These additions give CRGs and CAs the ability to parse and extract fields from context sensitive application protocols. These addit… Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1

Citation Types

0
4
0

Year Published

2016
2016
2023
2023

Publication Types

Select...
5
1
1

Relationship

1
6

Authors

Journals

citations
Cited by 17 publications
(4 citation statements)
references
References 14 publications
0
4
0
Order By: Relevance
“…Different services have different states on session connection or data flow [10]. A. X. Liu et al proposed a framework for automated online application protocol field extraction of DFI, which can effectively reduce the resources occupied by DFI and improve the running speed of the classifier [11].…”
Section: Related Workmentioning
confidence: 99%
“…Different services have different states on session connection or data flow [10]. A. X. Liu et al proposed a framework for automated online application protocol field extraction of DFI, which can effectively reduce the resources occupied by DFI and improve the running speed of the classifier [11].…”
Section: Related Workmentioning
confidence: 99%
“…In FPGA box, both OpenFunction script and pseudo language are translated to the special C/C++ code: the specification is translated to the top level block (composed by a call graph among low level blocks), while each pseudo language based action definition is translated to a low level block. The translation of data plane IPSEC specification (Algorithm 1) as shown in Algorithm 6, requires (1) defining the inter-link between functional actions (i.e., [5][6][7][8][9][10][11][12][13][14][15][16][17][18][19][20]; and (2) using direct function calls to represent actions (e.g., . Note that in FPGA platform, we implement all parameters as action attributes, which are controlled by its corresponding CP process.…”
Section: Script Supportmentioning
confidence: 99%
“…P4 improves OpenFlow by allowing users to extract customized packet header fields. However, many middleboxes, such as application firewalls and IPSes, need to match packet payload against signatures [8]. Third, the table abstraction in OpenFlow/P4 is fundamentally incapable of modeling the function of scheduling.…”
Section: Introductionmentioning
confidence: 99%
“…The traditional traffic identification methods include the deep packet inspection [2][3][4][5] and the deep flow inspection. [6][7][8] For the encryption traffic identification, the traditional identification method was faced with a series of issues. Moreover, it was difficult to match the encryption protocol by the load information, and it was easily affected by the upgrade of the protocol.…”
Section: Introductionmentioning
confidence: 99%