Point Connection · Server and container security
Protect critical assets with connected risk analysis and response
Analyze external exposure, vulnerabilities, and attack paths across network assets and services. Connect threat detection and response with compliance checks and audit evidence to manage risks to critical assets and prioritize action.
Prioritize response with impact in view
Identify points shared by multiple attack paths and review access restrictions and permission reduction first.
Unified inventory · Unmanaged asset discovery · Critical asset analysis
See coverage gaps and protection priorities with unified asset management
Review server, container, and Kubernetes assets in one place. Find devices missing from management , review risks that may affect critical operations, and identify assets to protect first .
Bring distributed assets together
Organize servers, containers, and services by type to review management status .
Review critical assets first
Reflect business importance and security classification to automatically analyze protection priorities .
Include unmanaged devices
Inspect open services on unmanaged devices and collection gaps in the environment.
| Asset | Type | Management status | Open services | Protected target |
|---|---|---|---|---|
| Server | Unmanaged | SSH · 22 | — | |
| ||||
| Server | Managed | HTTPS · 443 | — | |
| Service | Managed | HTTPS · 443 | Critical asset | |
| Container | Managed | Internal service | — | |
| Database | Managed | Internal service | Critical asset | |
| Server | Unknown | Not collected | — | |
Attack surface management · Attack path analysis · Automated response prioritization
See risks to critical assets and priority response points together
Analyze how exposed services and vulnerabilities connect to critical assets . Identify where to restrict access and update response priorities .
Review publicly exposed services
Find externally accessible assets and connections into the environment .
Analyze paths to critical assets
Review which assets a risk can pass through and how it may affect critical operations .
Identify where to respond first
Find points shared by multiple paths and consider access restrictions or reduced permissions .
Runtime security · Real-time behavior detection · Detection policy management
Identify suspicious activity during operation with real-time threat detection
Monitor privilege escalation, suspicious traffic, and security configuration changes in real time. Review detected behavior alongside related assets to identify what needs investigation.
Detect suspicious runtime activity
Analyze behavior on servers and services to identify signals to investigate .
Review detection trends and targets
Review detection trends over time to see which targets are affected .
Configure detection for your environment
Configure detection policies and rules, and manage indicator of compromise (IOC) target scope .
Incident investigation · Response approval and execution · Response history
Verify response outcomes with structured threat response
Review incident evidence and manage ownership and processing status. Execute the required action after review and approval , then track execution results and follow-up observations .
Investigate incidents using evidence
Review relevant evidence and manage incidents from assignment through closure and reopening .
Respond within approved scope
In supported environments, execute process termination, traffic blocking, and asset isolation .
Connect with security operations
Separate roles and permissions by project, with support for notifications and external log integration (Syslog and CEF).
Execution history
From request to execution result,
trace the response history
Review which action was executed on which target, with timestamped results and failure reasons.
Follow-up review
Review response effects and service status
separately
Review target state, service error rate, and latency after action to identify where further response is needed.
Risk-based vulnerability management · CVE analysis
Prioritize vulnerability remediation using exploitability and impact
Compare evidence of exploitation, fixed versions, and affected assets to identify vulnerabilities to fix first . Track issues without patches as targets requiring separate mitigation .
Locate concentrations of risk
Compare severity and exploitability to narrow which areas to review first .
Select vulnerabilities to fix now
Review exploitation evidence and patch availability to identify priority fixes .
Review affected assets and fixed versions
Review assets using vulnerable packages alongside installed and fixed versions .
Mitigation
Patch priority
Monitoring
Patch recommended
Understanding vulnerability analysis CVE · CVSS · EPSS · CISA KEV
CVE
An identifier for a known security vulnerability.
CVSS
A score representing the technical severity of a vulnerability.
EPSS
A prediction of future exploitation probability, distinct from confirmed exploitation.
CISA KEV
A catalog of vulnerabilities with confirmed exploitation, distinct from the availability of public exploit code.
Security compliance · Configuration checks · Audit evidence management
Connect check results to audit evidence with compliance management
Review each security standard to identify which controls need attention . Review affected assets and remediation guidance, then organize reassessment results and work records for audits .
Quickly identify controls to improve
Check technical controls in supported standards such as ISMS-P and CIS, distinguishing noncompliant and unevaluated states .
From findings to remediation guidance
Review affected assets and evaluation evidence, together with required remediation steps .
Turn check records into audit evidence
Connect reassessment results with remediation history to retain the evidence needed for audits .
Access control
Security settings
Log management
| Check area | Business server | Production server | Container | Storage |
|---|---|---|---|---|
| Access control | ||||
| Security settings | ||||
| Log management |
Remediation · Exceptions · Reassessment
Recheck remediation results and
manage exception expiry
Recheck compliance after remediation and manage the reasons and expiry dates of approved exceptions.
Audit package
Organize findings and remediation records
as audit evidence
Retain results and evidence for the selected standard, project, and period in one package.
Security operations value
Use analysis results
to guide action and investment
Clear owners and deadlines for
remediation management
Manage priority vulnerabilities with owners, deadlines, and progress .
Consider both risk and cost in
investment decisions
Review response costs and required remediation resources to support security investment decisions .
Review residual risk to
verify outcomes
Review vulnerable paths and residual risk after action, and use follow-up observations in the next response .
Frequently asked questions
Which assets and environments can we review?
Review devices discovered on the network, managed assets, and relationships across servers, containers, and Kubernetes. During adoption consultation, we explain deployment configuration and collection scope for your environment.
How do we verify remediation results?
Review command delivery and execution history separately from follow-up observations for security objectives and service status. Link failure reasons and follow-up commands to assess further action.
Can check results be retained for audits?
Select a standard, project, and period to organize findings, remediation and exception records, and evidence into an audit package. Manage package versions, retention periods, and delivery history.
Security for your environment,
together with WERANA.
Tell us about your servers and security challenges.
We will explain supported features, scope, and adoption requirements.