Take the following elements into consideration when designing, in order to achieve secure system operations using BDCEP:
Security roles
Protected resources
Threats to protected resources and their countermeasures
Overview of countermeasures for threats to protected resources
Security roles
The table below lists the types of system users that use BDCEP, their security roles, and the corresponding operating system user:
User type | Security role | Operating system user |
|---|---|---|
System administrator | Can perform all operations. Can perform operations involving CEP Server, such as starting and stopping the CEP Server or reconfiguring a CEP engine. | Superuser |
Engine execution user | Can run a CEP engine process. | Engine execution user |
Developer | Can deploy definition information to a CEP engine and undeploy it (to check the operation of definition information), as well as start and stop a CEP engine. | General user who can login to the CEP Server |
Protected resources
The table below lists the resources to be protected by the CEP Server.
Type | Protected resource | Description |
|---|---|---|
File | Engine configuration file | File used to reconfigure a CEP engine. |
Deployed definition information | Definition information deployed to a CEP engine. | |
Master data | CSV files to be referenced by the high-speed filter. | |
Resource log | Output file used to investigate the resource usage. | |
Engine log | File to which the detailed operation status of a CEP engine is output. | |
Custom log | Log file output by a user-developed Java class | |
Data for investigation | File collected to investigate faults. | |
Network | Event data sent to an input adapter | Packets traveling across the network. |
SOAP messages sent from an output adapter | ||
Communication when Terracotta collaboration is used to remotely access a cache | ||
Communication when Hadoop collaboration is used to remotely access a Hadoop system | ||
Communication when RDB collaboration is used to remotely access a relational database |
Threats to protected resources and their countermeasures
The table below lists the possible threats to protected resources, and their respective countermeasures:
Type of protected resource | Threat | Security countermeasure |
|---|---|---|
File | Tampering or destroying | Setting permissions Authenticating operation permissions for the CEP Server |
Network | Sniffing | Placing on a secure segment |
Overview of countermeasures for threats to protected resources
The table below provides an overview of each possible security countermeasure:
Security countermeasure | Overview of countermeasure |
|---|---|
Setting permissions | Set operating system permissions for files included in the protected resources. Set appropriate permissions to suit the security roles. |
Authenticating operation permissions for the CEP Server | Use operating system authentication. Only allow suitable users to login to the operating system. BDCEP assumes that users who are given authentication to login to the CEP Server can be trusted with operating a CEP engine and referencing an engine log. In addition, some operations, such as reconfiguring a CEP engine and starting and stopping the CEP service, can only be performed by a superuser. |
Placing on a secure segment | To inhibit data sniffing and hacking, place the CEP Server on a secure segment. |
