## 13.3.4.2.7.13.1.1  Communication Channel Security
## Use
The following table shows the communication paths that B2A: Communication with Authorities (PY-DE-BA) uses, the protocol used for the connection, and the type of data transferred.
| Communication Paths   | Protocol Used                                                                                                                                                                                                            | Type of Data Transferred   | Data Requiring Particular Protection   |
|-----------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------|----------------------------------------|
| ELSTER                | HTTP Internal: HRsystem -> Mid- dleware (BC or PI/PO): Com- munication channel RFC Middleware (CI): Communi- cation channel HTTPS External: Middleware (BC, CI, PI/PO) -> Tax authori- ties: Communication channel HTTPS | Personnel data             | Person-related data                    |
| eSTATISTIK.core       | HTTPS                                                                                                                                                                                                                    | Personnel data             | Person-related data                    |
| SI (DEUEV, …)         | HTTP/E-mail                                                                                                                                                                                                              | Personnel data             | Person-related data                    |
| ZfA/PRN               | VPN                                                                                                                                                                                                                      | Personnel data             | Person-related data                    |
##  Recommendation
We strongly recommend that you use secure protocols (SSL, SNC) where possible.
For more information, see the ABAP Platform Security Guide under Transport Layer Security.
## Communication Destinations
The following table provides an overview of the communication destinations that B2A: Communication with Authorities (PY-DE-BA) uses.
| Destination             | Provided   | Type      | Description                                                 |
|-------------------------|------------|-----------|-------------------------------------------------------------|
| HR_DE_ELSTER            | No         | RFC/HTTPS | Transfer of data for EL- STER to middleware (BC, CI, PI/PO) |
| HR_DE_ECORE             | No         | HTTPS     | Transfer of data for statistical data (Earnings Survey)     |
| HR_DE_GKV, HR_DE_RVBEA, | No         | HTTPS     | Transfer of data for GKV/ DSRV to health insurance          |
| HR_DE_DSVV,             |            |           |                                                             |
| HR_DE_DSRV              |            |           |                                                             |
| HR_DE_ZFA,              | No         | RFC       | Transfer of data for ZFA to middleware (BC, PI/PO)          |
| HR_DE_RBM_BC            |            |           |                                                             |
## Security-Relevant Logging and Tracing
- ELSTER: Tracing for error analysis using BI/BC is possible.
- eSTATISTIK.core: Tracing for error analysis using ICM (transaction: SMICM) is possible.
- SI (DEUEV, …): Tracing for error analysis using ICM (transaction: SMICM) is possible.
- ZfA/PRN: Tracing for error analysis using ICM (transaction: SMICM) is possible.