Skip to content

01KARAMOTECH / SECURITY SERVICES / SWITZERLAND

Know what needs attention. Know what to do next.

Your website may be running. Your accounts may be working. But do you know what happens when something fails—or who is responsible for fixing it?

I help small businesses and technical teams identify what is known, what needs verifying, and which improvements matter first. Clearly scoped work. Documented observations. No theatrical promises.

Human-led · Scope agreed before testing

KT / 001SECURITY REVIEW
Illustrative report structure — not client data

Security review / example

Scope → Evidence → Action

01ContextSystems and purpose
02ObservationsEvidence and limits
03PrioritiesWhat to address first
04Next stepsOwnership and verification
01—04CONFIDENTIALITY BY DESIGN
KARAMOTECHSECURITY / INFRASTRUCTURE / ACCOUNTABILITYCH · 2026

01Direct technical contact

02Written findings, not vague claims

03Testing only with permission

04Local in Rapperswil-Jona

QUESTIONS THAT MATTER

A healthy-looking system isn't the same as a well-understood one.

These are common gaps worth investigating, not claims about your environment.

ASSESSMENT / 01

Who can still access your business accounts?

Why it matters

Former staff, shared credentials and broad permissions can complicate account security.

First practical step

Review access, privileged accounts and offboarding responsibilities.

Try the guided IT check
CHOOSE THE RIGHT STARTING POINT

Three ways to get clarity.

The right engagement depends on your systems, your question and what testing you authorise.

BUSINESS IT01 / 03

Security Readiness Review

A practical discussion and review of account protections, update ownership, backups, remote access and recovery arrangements.

IDEAL FOR

Owner-managed businesses and small teams

POSSIBLE SCOPE

  • MFA and access responsibilities
  • Backup and recovery evidence
  • Updates, remote access and ownership

DELIVERABLE

Written observations, gaps to verify and a prioritised next-step list.

A readiness review is not a penetration test.

Ask about a readiness review
WEB SECURITY02 / 03

Website & WordPress Review

A focused look at how a business website is maintained and protected, with appropriately authorised technical checks where agreed.

IDEAL FOR

Small-business websites, CMS and WordPress owners

POSSIBLE SCOPE

  • Admin and hosting account hygiene
  • Updates, plugins and backups
  • Agreed configuration and selected application checks

DELIVERABLE

Scoped review notes with reproducible observations where applicable and remediation recommendations.

A website review does not guarantee a site is vulnerability-free.

Discuss my website
TARGETED TESTING03 / 03

Web Application & API Security Testing

A purpose-built technical assessment of an agreed application, feature or API, limited to the authorised targets and depth.

IDEAL FOR

Product owners, web teams and agencies

POSSIBLE SCOPE

  • Written scope, test windows and exclusions
  • Selected authentication, access and business-logic checks
  • Evidence, root-cause notes and responsible handling

DELIVERABLE

A technical report with verified observations, impact context and practical fixes; retesting by agreement.

Feasibility and depth are confirmed before an assignment; not every request is a full pentest.

Discuss a scoped test
HOW THE WORK RUNS

No mystery. No surprise testing.

  1. 01

    Talk through the concern

    We establish what matters to the business, what's already known and what outcome is needed.

  2. 02

    Agree the boundaries

    We confirm systems, approvals, exclusions, timing, deliverables and costs before touching anything.

  3. 03

    Review and verify

    We carry out the agreed review, distinguish confirmed observations from unknowns and avoid unnecessary disruption.

  4. 04

    Explain what to fix

    You get a clear written handover, prioritised recommendations and an option to verify changes separately.

SEE THE DELIVERABLE

A report your team can actually use.

Management needs the implications. Technical teams need evidence and steps. A good report should serve both.

01

Executive overview

What was assessed, the main observations, constraints and proposed priorities.

02

Finding detail

Clear description, evidence boundary, realistic impact and remediation advice.

03

Resolution plan

Suggested next steps, owners to involve and what still needs verification.

View the illustrative report

Our example uses fictional information and is not evidence of a completed customer test.

KARAMOTECH / REPORTEXAMPLE — 01

SAMPLE / FICTIONAL

Security Review

Example of a written handover

SCOPEDefined
OBSERVATIONEvidence gap
NEXT ACTIONRestore test

KARAMOTECH / ETHICS / 01

Research-led thinking, responsible delivery.

Independent vulnerability research teaches a valuable habit: separate what the evidence shows from what you merely suspect. The same discipline belongs in commercial security work. Unpublished research and customer information remain confidential.

How I approach security research
BEFORE YOU BOOK

Questions sensible buyers ask.

01Can you tell if our website is secure just by looking at the URL?

No. Public signals can inform a discussion, but a credible security finding requires a defined scope, access where appropriate, and reproducible evidence. We won't claim a site is safe or unsafe from a URL alone.

02What's the difference between the readiness review and a penetration test?

The readiness review examines responsibilities, configurations and available evidence against practical controls. A penetration test actively probes agreed targets for technical weaknesses within written rules of engagement. The latter needs more planning and a narrower technical scope.

03Do we need to share passwords or customer data?

Not for the first discussion. Any subsequent access must be specifically authorised and minimised; we agree how sensitive information is handled before work starts. Do not submit passwords in the web form.

04What exactly do we get?

We agree a deliverable before the work starts. Depending on scope, expect written observations, evidence limits, business relevance, recommended next steps and a technical section where applicable. The sample report shows the intended structure, not guaranteed findings.

05How much does a review cost?

There is no honest one-price-fits-all answer. We confirm the system, depth of testing, constraints and reporting needs, then provide a defined scope and quotation before starting.

06Can you work alongside our existing IT provider?

Yes, where all parties agree the boundaries. A second opinion, limited application review or independent verification can complement your existing IT team without taking over operations.

07Will you fix everything you find?

We can discuss practical remediation support where suitable. Findings, fixes and independent retesting should be distinguished, and any extra work is quoted and authorised separately.

START WITH THE REAL QUESTION

What are you most unsure about?

A short conversation can establish whether you need everyday IT support, a security readiness review or a properly scoped technical test.

DIRECT CONTACT

What would you like to discuss?

Tell me briefly what you need and where you are. We will work out the next step together.

+41 76 724 81 75

Assignments subject to confirmed availability. Scope and costs agreed before work starts.

Send your request

Please provide a phone number or email address.

Your details are checked by our Cloudflare endpoint and sent through Zoho Mail to handle your request. Please do not include passwords or credentials.

Privacy and service providers ↗

Preparing the enquiry form …