mirror of
https://github.com/amidaware/tacticalrmm.git
synced 2026-04-26 06:55:52 +03:00
[GH-ISSUE #2429] Is it possible to split management and agent connections? #3427
Labels
No labels
In Process
bug
bug
dev-triage
documentation
duplicate
enhancement
fixed
good first issue
help wanted
integration
invalid
pull-request
question
requires agent update
security
ui tweak
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/tacticalrmm#3427
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @rwright-bci on GitHub (Mar 6, 2026).
Original GitHub issue: https://github.com/amidaware/tacticalrmm/issues/2429
We had our annual NIST-CSF assessment/review today and TacticalRMM came into the conversation. They were wondering if there is a way to only have management access open on our inside network and not visible externally? We cannot close off all of Tactical since we have mobile users' devices reporting back. Not sure if its possible.
Gotta love these assessments. If we secured everything as they request, work would never get anything done! 😛
We host Tactical on our own infrastructure in our DMZ currently.