> For the complete documentation index, see [llms.txt](https://docs.fusion.vectra.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.fusion.vectra.ai/detection-models/library/misconfiguration/external_printing_connections.md).

# external\_printing\_connections

Explanation This event is designed to detect external connections to internal print servers. The event triggers when an external source tries to connect to a print server residing within the protected

**Explanation**

This event is designed to detect external connections to internal print servers. The event triggers when an external source tries to connect to a print server residing within the protected network. This event is helpful in identifying potential threats that may compromise the confidentiality or integrity of the network.

**What to Look For**

When analyzing the results of this event, it is important to look for any attempts by external sources to connect to internal print servers. This could indicate an attempted intrusion or a compromised endpoint on the network. It is also important to examine the print server logs for any unusual activity, such as unexpected print jobs or unauthorized access. Remediation should include isolating compromised endpoints, blocking unauthorized access attempts, and implementing stronger security measures to prevent similar incidents in the future.

**Related MITRE ATT\&CK Categories**

[Initial Access, Persistence: External Remote Services, Technique T1133 - Enterprise](https://attack.mitre.org/techniques/T1133)


---

# 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.fusion.vectra.ai/detection-models/library/misconfiguration/external_printing_connections.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.
