Enterprise mobility management (EMM) is the combination of technology, policies, and operating processes used to secure and manage mobile devices, applications, identities, and business data. It covers company-owned and employee-owned phones and tablets throughout their lifecycle, from enrollment and access through incident response and retirement.

EMM makes mobile work possible without treating every device as trusted by default. A practical program combines device management, app and data protection, identity controls, employee privacy, documented exceptions, and evidence that controls actually ran. This guide explains how EMM relates to MDM, MAM, BYOD, and unified endpoint management, then shows how to implement it without creating unnecessary friction.

The best IT Glue alternatives for MSP IT documentation are specialist documentation platforms, password systems, knowledge bases, discovery tools, and governed workflow platforms that solve different parts of the managed-service documentation problem.

IT Glue is a cloud platform for MSPs that need structured client documentation, credentials, assets, relationships, and integrations in one place. Teams compare alternatives when they want a different contract model, deployment option, credential workflow, discovery depth, RMM alignment, or a way to connect approved documentation to repeatable execution.

IT security processes are repeatable procedures that protect systems, data, access, networks, and incident response. The best ones do not live in someone’s head or a one-off spreadsheet. They are assigned, run, documented, and reviewed.

This IT security checklist covers eight practical workflows your team can run in Process Street: privileged password management, daily network administration, network security audits, firewall audits, VPN configuration, Apache server setup, email server security, and penetration testing.

Strong IT service management runs on repeatable processes, not heroics. This guide gives you eight free ITIL process templates you can run in Process Street right away, covering everything from incident, problem, and change management through to continual service improvement, so your team handles IT work the same reliable way every time.

ITIL, the Information Technology Infrastructure Library, is the most widely used framework for IT service management. It organizes the practices that keep IT services aligned with the needs of the business, from logging an incident to reviewing a change after it ships, and it is the backbone of first-class IT service management in most enterprises and government agencies.

Continue Reading

Documented processes for IT, MSPs, and system administrators are not optional. Client infrastructure depends on details: server names, router configs, vendor obligations, patch windows, escalation paths, and the small handoffs that break when they live only in someone’s head.

This post gives you seven IT process templates you can adapt for your own team: naming conventions, Cisco router setup, supplier evaluation, contract negotiation, service calls, scheduled maintenance, and patch management. Use them as MSP SOP templates, sysadmin runbooks, or starting points for standardizing recurring IT work in Process Street.

Continue Reading

How do you set up your servers? You probably just know how to, like it is an instinct. But is it the absolute best way to do it? Are you leaving holes in your security, or forgetting to add users that desperately need access? This pack gives sysadmins Apache, Ubuntu, proxy, FTP, Samba, and Windows setup checklists they can run and adapt.

Or, look at it another way: if you are the only one who knows your server setup methods, how are you going to train your team? Processes are a solid basis for your business expansion because the question of how to do a task is answered automatically, clearly, and consistently every time.

Continue Reading

Linux server security starts with hardening the basics: patching packages, reducing exposed services, tightening SSH, enforcing sane account controls, and monitoring for suspicious changes.

This Linux server hardening checklist pairs hands-on sysadmin commands with current context for cloud and VPS environments where a small missed setting can become a production incident.

Continue Reading

IT processes are the recurring workflows that help teams avoid server failures and client headaches by keeping technical work from becoming guesswork. They cover the things teams cannot afford to improvise: inventory, backups, server setup, incident response, helpdesk escalation, access control, and audits.

When those workflows are documented and run in Process Street, the work is easier to assign, automate, review, and prove. That matters for uptime, client trust, and workflow automation compliance, because every skipped step in IT can turn into a security issue, a support backlog, or a client headache.

Continue Reading

In this article, we’ll take a look at the foremost standard for information security management – ISO 27001:2013, and investigate some best practices for implementing and auditing your own ISMS.

Here is a summary of what we’ll cover in this Process Street article:

• ISO 27001: The basics & why standards are important
• Who needs ISO 27001?
• How to implement ISO 27001
• Free ISO 27001 checklist
• How to get ISO 27001 certified
• Integrating your ISMS with other ISO standards

If you just want the free checklist for implementing and auditing your ISMS, you can grab that here. Otherwise, read on!
Continue Reading

How do you name a new server, export config data, or fix that one really annoying bug that keeps popping up every 2nd Thursday? Well, create a runbook!

For prepared IT professionals, that information is stored in a runbook. A runbook is a set of standardized documents, references and procedures that explain common recurring IT tasks. Instead of figuring out the same problem time and time again, you can refer to your runbook for an optimal way to get the work done. What’s more, you can also delegate tasks and onboard employees more effectively if you have documentation to train them with.

Whenever you do a task, think of this quote:

“Will you remember how to do these things 6 months from now? I find myself having to re-invent a process from scratch if I haven’t done it in a few months (or sometimes just a few days!). Not only do I reinvent the process, I repeat all my old mistakes and learn from them again. What a waste of time.” — Tom Limoncelli, The Operations Report Card

In short, the less time wasted figuring out how to do a task, the better it’ll be for your business efficiency, productivity, and sanity.

This post will look at:

• The 2 types of runbook
• How to create a runbook
• Running your IT processes with Process Street
• Transfer workflow information into Pages

First, let’s look at two example runbooks to give context on what I’m going to talk about.
Continue Reading