> For the complete documentation index, see [llms.txt](https://docs.medcrypt.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.medcrypt.com/medcrypt-documentation/guardian/api-overview/api-reference/classes/classmedcrypt-guardian-transportinterface.md).

# medcrypt::guardian::TransportInterface

[Service::ConfigureTransport](/medcrypt-documentation/guardian/api-overview/api-reference/classes/classmedcrypt-guardian-service.md#function-configuretransport) required interface.

`#include <TransportInterface.h>`

## Public Functions

|                                                                                                                                       | Name                                                                                                                                                                                                  |
| ------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| virtual                                                                                                                               | [**\~TransportInterface**](#function-~transportinterface)()                                                                                                                                           |
| virtual [Status](/medcrypt-documentation/guardian/api-overview/api-reference/namespaces/namespacemedcrypt-guardian.md#typedef-status) | <p><a href="#function-applysecurity"><strong>ApplySecurity</strong></a>(const std::unique\_ptr< medcrypt::guardian::utilities::SafeString > & in\_parameters) =0<br>Security parameters receiver.</p> |

## Public Functions Documentation

### function \~TransportInterface

```cpp
inline virtual ~TransportInterface()
```

### function ApplySecurity

```cpp
virtual Status ApplySecurity(
    const std::unique_ptr< medcrypt::guardian::utilities::SafeString > & in_parameters
) =0
```

Security parameters receiver.

**Parameters**:

* **in\_parameters** implementation dependent encoding of security parameters

**Returns**:

* **OK** successfully applied security
* **other** any non zero failure code

**Return**: [medcrypt::guardian::Status](/medcrypt-documentation/guardian/api-overview/api-reference/namespaces/namespacemedcrypt-guardian.md#typedef-status)

The contents of in\_parameters are dependent on the type of transport implemented by the derived class.

An implemented ApplySecurity function should return [GuardianStatusEnum::OK](/medcrypt-documentation/guardian/api-overview/api-reference/namespaces/namespacemedcrypt-guardian-guardianstatusenum.md#enum-type) on success, and a non zero derivation defined code on failure.

The SafeString type can be treated as a normal std::string.

## Debugging and logging

Guardian does not create log files. Instead, logging is controlled by the application:

* Guardian logs to `stdout` and `stderr`, which appear in the terminal/CLI of the running application during execution. Look for specific error codes or connection failures in the output.
* **Custom logging:** Use `SetLoggingCallback` to redirect log messages to a callback function, stopping terminal output and allowing custom log handling
* **Log control:** Applications can control log level and verbosity.
* **Guardian Cloud UI**: Check the Guardian Cloud interface for additional error details and provisioning status.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.medcrypt.com/medcrypt-documentation/guardian/api-overview/api-reference/classes/classmedcrypt-guardian-transportinterface.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.