Covington, KY · Northern Kentucky & Greater Cincinnati
Get support(407) 335-1296

Security & support

Careful access.
Clear responsibility.

Good technical support starts with permission, an agreed task, and an understanding of the information involved.

WORKING PRINCIPLES

Safeguards to discuss in your engagement.

01

Authorization first

Work should be requested by the owner or a representative authorized to approve the systems and data in scope.

02

Appropriate access

Use access suited to the task and agree how remote sessions, administrative rights, and vendor involvement will be handled.

03

Relevant information

Share only the information needed to understand and perform the work. Use an agreed secure method for anything sensitive.

Before a remote support session.

Confirm the request through a known contact route and understand what the technician needs to do. An unexpected caller should not receive access to your computer merely because they say they represent an IT company.

Close unrelated sensitive documents before a session. Enter your own password when required rather than disclosing it by email or text. Clarify whether the work requires attended or ongoing access and when any access should be removed.

JHProIT does not need your banking password or an unrelated one-time verification code to discuss a service inquiry. Report suspicious messages using the published support contact.

For business information and regulated environments.

Identify confidentiality, data-processing, retention, insurance, or regulatory requirements before the engagement is accepted. Ask for the relevant written scope and supporting information where required by your organization.

Our cybersecurity services include practical reviews and configuration assistance. This website does not claim SOC 2, ISO 27001, HIPAA, PCI DSS, or another audit or certification. A technical service does not replace a formal compliance assessment.

The Privacy Policy explains website and inquiry information handling. The applicable service agreement should address any additional processing needed for the work itself.

Report a suspected issue.

For a suspected issue with this website, use the contact page. Include the affected page, time, and a concise description. Do not include credentials or customer records.

Avoid accessing data that is not yours or performing disruptive tests. Reporting a concern does not grant permission for intrusive testing. For an active service incident, use the support route in your agreement and describe the business impact.

USEFUL NEXT STEPS

Keep the details connected.