Credential security
We keep passwords, keys and other credentials in secure stores. We configure which applications and users can use them so they are not left exposed in code or configuration.
Who can access your data, what AI is allowed to do and how the system responds to an attack. We address these questions during design and development. Our subsidiary comma0 helps with audits, risk management and monitoring.
We keep passwords, keys and other credentials in secure stores. We configure which applications and users can use them so they are not left exposed in code or configuration.
We separate parts of the network and allow only the connections applications need. We connect internal services privately so they do not need to be accessible from the internet.
We configure access, communication and application runtime rules in Kubernetes. The same rules apply to new instances as workloads grow.
We check the external libraries and other software components applications use. Configured rules determine which components developers and automated tools can download.
Powered by Shieldoo GateWe configure which data AI can access based on the signed-in user’s permissions. We also define which queries and responses are recorded. We work with comma0 to assess additional security requirements.
Before deployment, we automatically check components for known vulnerabilities and code for exposed passwords or keys. Releasing a new version depends on passing the agreed security checks.
Solution design based on Zero Trust principles: identity, network, encryption, key management and logging. We work with comma0 on requirements, risk management and documentation.
We review code and design, describe identified security risks and recommend which fixes to prioritise by risk impact and remediation effort. This helps you direct your budget towards the most important measures. We also assess systems built by other providers or before launch.
Security checks as part of the pipeline: dependency and image scanning, secret detection, SBOM, artifact signing. We set it up, train your people and hand it over.
Assessment of AI Act requirements, rules for query and response records, access permissions and environment selection based on data location and processing requirements.
We configure package and container image checks between your registries and dependency download tools. We adapt the rules to your development and operations.
Powered by Shieldoo GateWe have developed payment terminals and applications for PKI and certificate management running in the cloud and at end customers. We have experience with HSMs and development for payment environments with PCI requirements.
comma0 is our cybersecurity subsidiary. Together, we cover technical design, risk management, security testing and operational monitoring. We agree the division of work for each project.
Processes, policies and risk assessment. Assessment of relevant ISO 27001, ISO 22301, DORA, NIS2 and NIST requirements, proposed measures and audit documentation.
Round-the-clock monitoring with SIEM and SOAR, incident detection, response and support for service recovery.
Simulated real-world attacks against your defences. Find the weak spot before someone else does.
Infrastructure design based on Zero Trust principles, with technologies selected to suit the project’s needs.
Tell us what costs you the most time, money or operational effort. Together, we will choose a first step and a way to measure its benefits.
info@cloudfield.czThe site does not work without strictly necessary cookies, so those are always on. Traffic and LinkedIn campaign measurement only switch on with your consent. Rejecting is as easy as allowing – no hard feelings. Privacy policy
The site does not work without them. We set just one, and it remembers what you chose in this banner.
cf_consent · cloudfield.cz · 1 year — Stores your cookie settings choice.Google Analytics shows us how many people visit the site and what they read. It does not tell us who you are.
_ga · Google · 2 years — Distinguishes visitors for traffic statistics._ga_2FE6EFFNHT · Google · 2 years — Keeps session state for Google Analytics 4.The LinkedIn Insight Tag measures whether our LinkedIn campaigns are any good. LinkedIn may link the visit to your profile while doing so.
li_sugr · LinkedIn · 3 months — Probabilistic browser identifier for campaign measurement.bcookie · LinkedIn · 1 year — Identifies the browser for LinkedIn services.lidc · LinkedIn · 1 day — Routes requests to LinkedIn's servers.UserMatchHistory · LinkedIn · 30 days — Syncs identifiers for LinkedIn advertising.AnalyticsSyncHistory · LinkedIn · 30 days — Time of the last sync with the lms_analytics cookie.li_fat_id · LinkedIn · 30 days — Attributes a site visit to a click on a LinkedIn ad.