Member Avatar for jino.john

Hello All,

We are starting a linux/unix remote server administration service in india. we have a group of 4-10 years industry experienced, RHCA, SCNA certified, people.

we can install/monitor/configure any of your linux/solaris based system/service from india around the world.

pls reply me back on the thread only..

Thanks, Regards

Jino John

  • 2 Contributors
  • 2 Replies
  • 125 Views
  • 5 Days Discussion Span
  • Latest Post Latest Post by jino.john

Dani AI

Generated

Remote administration is useful but raises predictable trust and security questions. The original offer from and the blunt critique from highlight two things: providers need to demonstrate competence and customers need to verify controls. The short checklist below lists practical items that protect both sides and make a remote-admin engagement workable and auditable.

  • Written scope and SLA: hours covered, alert response times, escalation matrix, maintenance windows, and handover conditions.
  • Verifiable references and at least one recent case study or sample runbook for a similar environment.
  • Onboarding checklist: signed NDA, account creation rules, temporary credentials, and explicit credential revocation steps at contract end.
  • Access controls: no shared root passwords, SSH key-based access via a bastion/jump host, time-limited sudo, and 2FA for privileged accounts.
  • Monitoring and alerts: which tools are used, who receives alerts, test alerts schedule, and integration with incident management.
  • Backup and DR proof: backup schedule, encryption, offsite retention, and periodic restore tests with documented results.
  • Change control and patch policy: how changes are proposed, approved, tested, rolled back, and logged.
  • Liability and insurance: clear contract terms for damages, data loss, and breach notification timelines.

Minimal technical controls to expect: configuration management (Ansible/Puppet/Chef) with versioned playbooks, centralized logging and audit trails, regular vulnerability scans, documented runbooks for common incidents, and periodic DR exercises.

A concise, professional initial post from a provider that lists a sample SLA, onboarding checklist, and one or two references will answer the presentation concerns raised by . For long-term safety, insist on staged access (test/staging first), documented procedures, and a final handover with all credentials and logs when any engagement ends.

Member Avatar for killer2021

"Linux/Unix Remote Administration."


If you can't even get that right, what can you get right? probably nothing. The least I would want you doing is monitoring my servers.

Member Avatar for jino.john

Hi,

I didnt understand ur idea.

Thanx

Jino John

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.