# Security with Roon ARC / Roon 2.0

**URL:** <https://community.roonlabs.com/t/security-with-roon-arc-roon-2-0/206917>\
**Category:** Feedback\
**Created:** [July 15, 2022, 12:36pm UTC](https://community.roonlabs.com/t/security-with-roon-arc-roon-2-0/206917 "2022-07-15T12:36:54Z")\
**Posts on this page:** 1\
**Showing post:** 172

<div class="post-metadata">

**Author:** ![Jacques\_Distler](https://community.roonlabs.com/letter_avatar/jacques_distler/32/5_5575768a8748004e209b776fc1b2916d.png) [@Jacques\_Distler](https://community.roonlabs.com/u/Jacques_Distler)\
**Post date:** [September 21, 2022, 3:07pm UTC](https://community.roonlabs.com/t/security-with-roon-arc-roon-2-0/206917/172 "2022-09-21T15:07:27Z")

</div>

> [@Julian](#):
>
> Yes. I just tested my setup with a GRC Shields Up probe to the specific port that Roon Core opened up and I got “Status OPEN! - Unknown protocol for this port - Unknown application for this port”. I agree that it would be much more reassuring if Roon Core could not respond at all except to legitimate traffic.

What does that mean?

How do you decided whether the traffic is “legitimate” until after doing the TLS handshake, and the client has authenticated itself?

- The port is “open” because clients have to be able to connect to it.
- The protocol is HTTPS.
- The application is, of course “unknown” because it was just released yesterday.

---

_[View the full topic](https://community.roonlabs.com/t/security-with-roon-arc-roon-2-0/206917)._