Endpoint Security Monitoring & IT Approvals

Explore security & controls in detail.

Security & controls

Antivirus, firewall & encryption

Review device security readings and encryption state. Use authorised security actions according to the device and policy.

Close explanation of Antivirus, firewall & encryption

What it does

Bring supported endpoint security readings into the same view as device health. The team can review protection and encryption state, investigate missing or outdated evidence and use authorised actions where the device and customer policy allow them.

How you can use it

• Protection visibility. Review available antivirus and firewall readings, including relevant findings that need investigation rather than assuming all installed security software is functioning.
• Encryption context. Inspect supported disk-encryption state and connect permitted BitLocker actions or recovery-key handling to the device’s controls.
• Evidence for follow-up. Use the readings in alerts and readiness reviews, then inspect a fresh result after an eligible corrective action.

In practice

A support provider sees outdated supported antivirus definitions on a workstation and reviews the applicable correction and subsequent reading.

Controls & availability

Supported Windows actions are specific to the reported product and state. Vycko does not replace an antivirus product, and missing security evidence is not presented as proof of protection.

Ask us about Antivirus, firewall & encryption

Security & controls

Vulnerability & support status

Identify known application and operating system findings from configured vulnerability data, with exceptions and mappings for review.

Close explanation of Vulnerability & support status

What it does

Use configured vulnerability and support data to identify software that deserves attention. Vycko relates available application and operating-system information to known findings, helping the team prioritise investigation and update planning.

How you can use it

• Known findings. Review the available matches against the configured data sources, with the relevant application or operating-system evidence in context.
• Support lifecycle. Identify reported software or systems whose support status may create a maintenance or replacement decision.
• Review uncertain matches. Manage supported mappings and exceptions so ambiguous inventory is investigated rather than treated as a perfectly certain match.

In practice

A business review finds machines reporting an unsupported Windows release. The team can check the evidence and discuss an upgrade or replacement plan.

Controls & availability

Coverage depends on inventory quality, configured sources and matching. These checks do not establish that every vulnerability has been found or replace a full security assessment.

Ask us about Vulnerability & support status

Security & controls

Cyber Essentials readiness

Review technical readiness from available endpoint evidence and explore supported corrective actions. Readiness evidence is not certification.

Close explanation of Cyber Essentials readiness

What it does

Understand the available technical evidence relevant to Cyber Essentials preparation. Vycko brings supported endpoint checks into a readable readiness view, helping the team identify gaps and discuss the corrective work that may be needed.

How you can use it

• Evidence and coverage. Review the supported checks with their device coverage and freshness, so a headline is grounded in what has actually been observed.
• Findings to investigate. Open the affected devices and supporting readings when a technical condition needs attention.
• Supported corrective actions. Where a check has an eligible remedy, review that action through the applicable customer policy and approval workflow.

In practice

A company preparing for an assessment uses the readiness view to investigate endpoint update and protection gaps before discussing its formal assessment with the appropriate provider.

Controls & availability

The feature provides technical evidence and preparation guidance, not certification. Stale, unknown or unsupported checks remain explicit and are not counted as a pass.

Ask us about Cyber Essentials readiness

Security & controls

ISO 27001 technical readiness

Explore available technical control evidence and a customer checklist for other controls. Unsupported or unknown checks remain explicit.

Close explanation of ISO 27001 technical readiness

What it does

Connect supported technical evidence to an ISO 27001 readiness discussion without suggesting that endpoint data covers the whole management system. Vycko combines available technical checks with a separate customer checklist for areas requiring organisational evidence.

How you can use it

• Supported technical controls. Review the endpoint evidence the platform can judge, with coverage and known limitations shown alongside the finding.
• A broader checklist. Record customer input for organisational, people and physical areas that cannot be established from a computer’s telemetry.
• Clear gaps. Keep unsupported, not-checked and unknown areas visible so the team knows where additional evidence or specialist work is needed.

In practice

A business uses supported endpoint findings as one input to its readiness work, then gathers the policies, process records and other evidence needed outside Vycko.

Controls & availability

This is a readiness aid, not an ISO 27001 audit, certification or guarantee of conformity. Customer checklist answers and endpoint checks represent different kinds of evidence.

Ask us about ISO 27001 technical readiness

Security & controls

Approvals & customer rules

Define diagnostics-only, approval-required, pre-approved or prohibited actions. Important decisions stay visible and attributable.

Close explanation of Approvals & customer rules

What it does

Decide what level of autonomy suits each environment. Vycko’s rules distinguish observing a computer from changing it, and make an approval decision specific enough for the person reviewing it to understand the proposed work.

How you can use it

• Different action policies. Configure supported diagnostics-only, approval-required, pre-approved or prohibited routes according to the action and customer.
• Reviewable proposals. See the intended change, its device scope and relevant evidence before approving or declining a supported plan.
• Accountable decisions. Keep the decision and action connected in the record, with additional authentication or explicit server approval where required.

In practice

A household allows routine observation but wants repairs approved. A business uses tighter rules for its server than for eligible workstations.

Controls & availability

Approval applies to the plan that was reviewed. Changes to the material scope, procedure or parameters can invalidate that approval, and current policy is checked again before work starts.

Ask us about Approvals & customer rules

Security & controls

Secrets, keys & local passwords

Keep supported credentials and recovery keys in the vault, with controlled reveal, access records and rotation features.

Close explanation of Secrets, keys & local passwords

What it does

Keep supported credentials and recovery information within a controlled vault workflow. Vycko separates ordinary device visibility from revealing sensitive values, with customer scope, permissions and records around access.

How you can use it

• Protected storage and reveal. Store supported secrets using the vault’s encryption controls and require the applicable authorisation and fresh authentication before revealing a value.
• Managed local passwords. Use supported local-administrator password management and rotation workflows rather than sharing one static password across an estate.
• Recovery-key handling. Use supported BitLocker recovery-key escrow and related actions where configured, with device context and audit records.

In practice

An authorised technician needs a stored recovery value for an agreed support task, completes the required verification and leaves an auditable access record.

Controls & availability

Vault access is restricted and recorded. Supported key types and rotation depend on the device; Windows BitLocker support does not imply equivalent FileVault recovery-key escrow.

Ask us about Secrets, keys & local passwords

Security & controls

Stop controls

Pause the relevant automation, AI work or remote access when the environment needs it. Bound actions to the permitted scope.

Close explanation of Stop controls

What it does

Pause the relevant work when the environment or investigation needs a human decision. Stop controls give the team an explicit way to restrict supported automation, AI activity or remote access within the applicable scope.

How you can use it

• Scoped restrictions. Apply the relevant control to the affected environment instead of relying on someone to remember a note before starting work.
• Observe-only operation. Use supported settings to retain the permitted diagnostic picture while preventing the applicable changing actions.
• Checks as work begins. Current stop state is considered by the supported dispatch and start workflow, including relevant scheduled and remediation tasks.

In practice

During investigation of an unexpected application problem, a business pauses applicable automated changes while the team reviews the evidence and agrees the next step.

Controls & availability

A stop request cannot always undo a task already running. Some procedures finish at a safe point, and the resulting record explains work that could not be interrupted.

Ask us about Stop controls

Security & controls

External exposure checks

Review configured external checks for a customer’s public-facing services, within the customer’s approved scope.

Close explanation of External exposure checks

What it does

Review supported checks of a customer’s authorised public-facing services. This complements endpoint information by looking at the approved external scope, with findings available for the team to investigate.

How you can use it

• Explicit scope. Configure the permitted customer public addresses and retain the authorisation relevant to checking them.
• External findings in context. Review the supported exposure results with their target and timing rather than treating a computer’s local security state as the whole picture.
• A route to follow-up. Use findings to prioritise investigation of an unexpected public service or configuration and discuss the appropriate corrective work.

In practice

A business authorises checks of its public service addresses. The support team reviews an unexpected exposed service and confirms whether that exposure is intentional.

Controls & availability

External checks are off until configured and authorised, and only the approved scope is eligible. They are not unrestricted network scanning, penetration testing or a guarantee of external security.

Ask us about External exposure checks

Features depend on the device, operating system, installed agent and configured permissions. Readiness checks provide evidence and guidance, not certification. The website tour uses illustrative data and does not connect to live devices.