Elkaza Consulting · For SMEs in Vienna and Austria
A concept for stable IT infrastructure in growing teams.
Elkaza is being developed as a possible future offering for networks, access, backups, and documented IT operations.
The first step
A controlled starting point instead of a large rebuild on guesswork.
1. Capture current state
Review network, access, backups, cloud services, and admin accounts.
2. Prioritize risk
Check MFA, patch status, restore readiness, and public exposure.
3. Plan implementation
A practical roadmap with quick wins, effort, and the next step.
Sound familiar?
VPN keeps dropping
Home office outages, team complaints, lost productivity.
Firewall sprawl
No one knows which rules are active or why.
No runbooks
Incidents take too long. Every outage is improvisation.
Access rights unclear
Former employees still have access. Who can do what is not documented.
Backups never tested
Backup runs, but no one knows if restore actually works.
Choose the right starting point
Three clear paths depending on whether you need clarity, implementation, or ongoing operations first.
Assessment
Understand current state, risks, and prioritized actions.
View StarterSecurity Baseline
Improve MFA, admin access, backups, patch status, and documentation.
View BaselineManaged Operations
Monitoring, patching, backup checks, and clear incident response.
View OperationsPlanned service areas
These areas show how a future offer could be structured: stabilize the network, build a security baseline, secure access, or automate recurring IT work.
Network & Infrastructure
Stable connections, clean segmentation, secure remote access.
Security Baseline
Start here: Practical security for SMEs (MFA, patching, backups) – the foundation.
Zero Trust & Identity
Modern access control: MFA, conditional access, role-based permissions.
Automation & Platform Engineering
Infrastructure as Code, config automation, standardized deployments.
How the model is planned
Status
Project currently in preparation.
Analysis
Planned review of current state, risks, and quick wins.
Concept
Possible roadmap for security and stability.
Implementation
Later only after a clear legal offer.
Operations
Ongoing support is sketched as a possible model.
Why Elkaza?
Pragmatic, partnership-oriented, technically sound.
The focus is on clear, documented, and operable technical work.
- Handover pack: documentation, runbooks, access list
- Baseline metrics: patch status, backup health, MFA coverage
- Clean segmentation instead of flat network
- Monitoring from day 1, alerting on critical events
- Dedicated contact, clear communication
- Measurable results where possible
Illustrative Scenarios
Network Modernization for Retail Company
Security Baseline for IT Service Provider
Frequently Asked Questions
Answers to your most important questions
How long does a project take?
It depends on scope. The Security Baseline Assessment takes 1-2 weeks, implementation typically 2-6 weeks. Managed Services run continuously.
Will implementation disrupt our operations?
No, we schedule changes outside business hours and test thoroughly. For critical systems, we ensure rollback capability.
What happens after the project?
You receive full documentation, runbooks, and training. You can then engage us for Managed Services or continue independently.
Can these models be ordered already?
No. The models shown only document the current planning stage and are not offers.
Are prices already fixed?
No. Prices, scope, and contract terms will only be defined before a future market launch.
Do you guarantee 100% security?
No one can. We build a solid security baseline per best practices, with regular updates and monitoring.
What response time is planned?
Response and service hours are not yet defined and are not currently guaranteed.
Do you help with compliance (ISO, GDPR)?
Yes, we offer NIS2/Compliance Readiness. It's not an audit seal, but audit-ready security fundamentals.