Server security risks:
from inspection to action plans
MiWork Guard checks Linux vulnerabilities, malicious packages, risky settings and attack signals over SSH without installing an agent, then organizes what to fix first into an action plan.
AI organizes evidence and risks.
Administrators decide how to respond.
Identify which advisories apply to your servers and organize what to fix first.
Key features
Want to know what can be inspected in your server environment? Talk to our team →
Prioritize the work,
not just the findings
Group findings into work such as OS updates and image rebuilds, prioritized from P1 to P4.
- —Show packages, current/target versions and locations per action
- —Separate unclear production usage as “Verify usage”
- —Share reports, Excel and CSV exports with the responsible teams
Distinguish what was checked
from what was missed
No findings does not mean a server is safe. Show the verification status of all seven inspection areas, including what could not be checked.
- —The report opens with verified facts, remaining risks, unverified scope and recommended actions
From inspection to report
Inspections do not patch, delete files, stop services or reproduce attacks.
Web console and CLI,
the same permissions
Manage servers, inspection profiles, schedules and advisory data in a Korean-language web console. Use the command-line tool (CLI) where a browser is unavailable.
Administration is accessible only from allowed addresses. Server credentials and AI model keys are stored encrypted.
Common use cases
- Respond to urgent vulnerability advisoriesUpdate advisory data and inspect again to locate affected software and actions.
- Inspect supply-chain risksFind where publicly identified malicious packages are present.
- Regular air-gapped server checksImport advisory files and run scheduled inspections.
- Share security inspection resultsSend action plans and coverage reports to responsible teams.
Deployment and operations
- —Operate from one management server
- —Update vulnerability data online or import files; prepare OS package advisory data separately
- —Back up and restore configuration, inspection history and reports together
Ubuntu Linux is the primary supported management server environment. Target server compatibility and processing scale are reviewed for your deployment.
Frequently asked questions
What must I install on target servers?+
No separate collector is installed. Guard connects with a registered SSH account, reads data with predefined commands and checks versions of existing programs on servers and containers. Standard Linux commands and read permissions are required; containers need inspection permissions. Inaccessible areas remain uncollected. Privileged items are collected only when authorized in advance; server permission settings are not changed.
Which servers and software can be inspected?+
Linux servers accessible over SSH and their running containers are in scope. OS and app packages are compared with vulnerability data, and versions are collected for key runtimes and web servers. Assessment scope varies by item and is confirmed during planning. Windows servers and Kubernetes are not currently in scope; stopped containers are marked uncollected.
Does it certify that a server is safe?+
No. Reports show risks found within the inspected scope alongside unverified areas. A vulnerable version or attack signal alone does not confirm a breach. Guard does not guarantee detection of undisclosed zero-day vulnerabilities.
How are priorities determined?+
Findings are grouped from P1 to P4 by severity. Within a level, evidence that software is installed and running takes priority. This is not a calculated exploitability score; each item includes its ranking rationale.
Can it operate on an air-gapped network?+
Yes, with the required vulnerability data and an internal AI model if used. Download advisory data on an internet-connected PC, import the files and have an administrator review and apply them. Required data and import procedures are discussed during deployment. AI review can use an internal model or be omitted. Absence of external traffic is verified in your environment.
Does AI execute commands on servers?+
No. AI cannot run arbitrary commands. Optional follow-up investigation permits only predefined queries within an allowed scope. Extra collection using additional tools requires administrator approval. Secrets such as passwords and keys are masked before AI review, but not all sensitive data is guaranteed to be removed. Administrators decide whether external models may be used.
Are problems fixed automatically?+
No. Action plans provide target versions and example commands. Responsible staff decide on and perform remediation, then inspect again to verify it.
Will inspections affect server operations?+
Profiles set limits such as execution time and files read, and prevent overlapping inspections on the same server. Inspections are not load-free, so they can be scheduled during quieter hours.
Evidence first. Fix what matters first.
Review a MiWork Guard configuration for your servers, containers, air-gapped requirements and available AI models.