Cybersecurity
Application security services and cloud security
We review the applications you build, assess and harden the AWS, Microsoft Azure or Google Cloud accounts they run in, and design how the data they hold is protected. Reviews follow OWASP, and cloud work follows the CIS Benchmarks.
Overview
Applications, the cloud accounts they run in and the data they hold tend to fail together. A storage bucket left open exposes the data an application wrote to it. A permission granted too widely in the cloud lets a small flaw in the code reach far more than it should. Data copied to a backup nobody remembers is outside every control the application has. That is why we sell these three kinds of work as one service: an application security review, a cloud security assessment with the hardening that follows it, and the design for protecting your data. You can buy any one of them on its own, and the scope says which you need.
The work is part of our Cybersecurity practice. Application reviews follow OWASP, and cloud work follows the CIS Benchmarks for AWS, Microsoft Azure and Google Cloud.
Who it suits
This service suits companies that build or run their own applications in the cloud and hold data that customers, employees or partners trust them with. Typical reasons to start are a security questionnaire from a large customer, an audit on the calendar, an application about to launch, or cloud accounts that grew faster than anyone designed them.
It does not suit a company that wants its running application attacked to see what breaks. That is a penetration test, which our Red Teaming & Penetration Testing service covers. Nor does it suit a company looking for someone to watch its systems around the clock: we don't run a monitoring service or a security operations centre.
Cloud security assessment and hardening
A cloud security assessment reviews your accounts against the CIS Benchmarks, the configuration standards published for AWS, Microsoft Azure and Google Cloud. We look at who and what can do what, which services are reachable from the internet, how storage and databases are protected, whether data is encrypted, and whether the logs you would need after an incident are being kept. Each gap is ranked by how much it matters to you, not only by how the benchmark scores it, so the first fixes are the ones that close the most risk.
Hardening is the work of closing those gaps, and there is more than one way to do it. We can make the changes in your accounts ourselves, with your approval for each one. We can write them as infrastructure as code, so the secure settings live in your repository and stay in place when the environment is rebuilt. Or your own engineers can make the changes with our guidance, which suits teams that want to learn the work as they go. The scope says which, and a project can mix them.
Application security review
An application security review looks at an application from the inside. It starts with the design: how users sign in, how permissions are checked, which services the application calls and what it trusts. From that we build a threat model, a structured account of how the application could be attacked, which is most useful early, while changing the design is still cheap.
The code review follows OWASP guidance, such as the Top 10 and the Application Security Verification Standard. We read the parts of the code that handle sign-in, permissions and user input by hand, because that is where the serious flaws usually are, and run automated scanning across the rest. We check the third-party libraries the application depends on for known vulnerabilities, and the repository for passwords, keys and tokens committed by mistake, including in its history.
Every finding is written for the developer who will fix it, with the evidence, the location, how serious it is and how to fix it. Once the fixes are in, we recheck them, so the report ends with what is closed as well as what was found.
Data protection design
Protecting data starts with knowing where it is. We map the sensitive data across your applications, databases, cloud storage and backups, and label each kind by how sensitive it is and which rules apply to it. Customer records, financial data and employee files each carry different obligations.
The design then sets how each kind of data is protected: encryption at rest and in transit, who manages the keys and how they are rotated, which people and services can read the data, and how every access is logged so it can be checked later. We map the design to the privacy laws that apply to you, in the United States, in Mexico or both, so your legal and compliance teams can see which requirement each control answers.
The standards behind the work
OWASP is a nonprofit foundation that publishes open guidance on application security, and the CIS Benchmarks are consensus-based configuration guidelines that the Center for Internet Security publishes for each major cloud. We use them because your developers, your customers and your auditors already recognise them, and because they make our findings easy to check. Following a standard is not a certification, and this work does not certify an application or a cloud account.
Deliverables
What you get
- Cloud security assessment
A review of your AWS, Microsoft Azure or Google Cloud accounts against the CIS Benchmarks, covering identity and permissions, network exposure, storage, encryption and logging, with each gap ranked by how much it matters.
- Cloud hardening
The changes the assessment calls for, made in your accounts by us, written as infrastructure as code your team keeps, or applied by your own engineers with our guidance, as agreed in the scope.
- Application design review and threat model
A review of how the application is built, from sign-in and permissions to the services it calls, and a threat model of how it could be attacked, written so it is useful before or during development.
- Source code review
A review of the application's code against OWASP guidance, combining a manual read of the parts that handle sign-in, permissions and user input with automated scanning across the whole codebase.
- Dependency and secrets review
A check of the third-party libraries the application depends on for known vulnerabilities, and of the repository for passwords, keys and tokens that should never have been committed.
- Findings report and recheck
Every finding with its evidence, where it is, how serious it is and how to fix it, written for the developers who will make the change, followed by a recheck once the fixes are in.
- Data inventory and classification
A map of where your sensitive data lives, across applications, databases, cloud storage and backups, with each kind of data labelled by how sensitive it is and which rules apply to it.
- Data protection design
The design for protecting that data, covering encryption at rest and in transit, who manages the keys, who and what can read each kind of data, how access is logged, and the privacy laws that apply.
Process
How an engagement runs
- 01
Agree the scope
We agree which cloud accounts, applications and data are in scope, which deliverables you need, and who on your team answers questions. Access is read-only for assessment work, and nothing is reviewed without written authorisation.
- 02
Learn the systems
Your engineers walk us through how the applications are built and deployed, which cloud accounts they run in and where the data goes. We read the documentation and plan the review around what matters most.
- 03
Assess and review
2 to 6 weeks
We assess the cloud accounts, review the application's design and code, and map the data, recording each finding as we go so nothing waits for the final report.
- 04
Report and walk through
You receive the report, and we walk your engineers through it so that every finding is understood, ranked and assigned before anyone starts on a fix.
- 05
Harden and design
2 to 4 months
Where the work goes further, we harden the cloud accounts and design the data protection with your team, then recheck the fixes and hand over the documentation.
Proof
Credentials and partners
Marco Villarruel, Founder & CEO
- C|CSE
- CASE
- Amazon Web Services
Registered partner in the AWS Partner Network
- Microsoft Azure
Member of the Microsoft AI Cloud Partner Program
- Google Cloud
Select tier partner in the Google Cloud Partner Network
FAQ
Frequently asked questions
How long does it take and how is it priced?
A cloud security assessment or an application security review takes two to six weeks and is fixed price, with what is in scope named before we start. Cloud hardening and data protection design take two to four months and are priced as a fixed fee or as time and materials. The number of cloud accounts, applications and data stores sets most of the effort.
What is the difference between an application security review and a penetration test?
A review works from the inside. We read the design and the code, check the libraries and the repository, and find weaknesses before they can be reached, often before the application is live. A penetration test works from the outside, attacking the running application the way an attacker would, to show what can actually be exploited. The two find different things, and many companies use both. Penetration testing is a separate service, so a test can check the fixes a review led to.
Which cloud do you work with, and can you cover more than one?
We work with Amazon Web Services, Microsoft Azure and Google Cloud, and with companies that use more than one of them. Each cloud has its own CIS Benchmark, and an assessment checks each account against the benchmark for its provider, then looks at how identity and data move between them. We don't resell licences or cloud services, so our advice is not tied to any provider.
Will this help us answer a customer's security questionnaire or an audit?
Yes. Questionnaires and audits ask how your applications are reviewed, how your cloud accounts are configured and how sensitive data is protected. The assessment report, the review findings with their recheck, and the data protection design are documents you can point to as evidence. If the request is for a formal certification such as ISO/IEC 27001 or SOC 2, our compliance work prepares you for the audit itself.
Related
Related services
Red Teaming & Penetration Testing
Penetration testing services for web apps, APIs, networks, cloud and Active Directory, plus red teaming. Every test ends with a report and a retest.
ExploreThreat Detection & SIEM Implementation
SIEM implementation on Microsoft Sentinel, Splunk, Elastic Security or Wazuh, with log sources, detection rules and runbooks handed to your team.
ExploreSecurity Governance
We design your information security program on ISO/IEC 27001 and NIST CSF, with policies, risk and metrics reporting, and a process for assessing suppliers.
ExploreCloud Transformation
Cloud migration services to AWS, Microsoft Azure or Google Cloud: a landing zone, infrastructure as code, the migration itself and cloud cost optimization.
ExploreThe engagement
- Duration
- 2 to 6 weeks; hardening and design 2 to 4 months
- Pricing
- Quoted for each engagement
Assessments and reviews are fixed price. Hardening and design are fixed price or time and materials, agreed in the scope before work starts.
- OWASP
- CIS Benchmarks
Next step
Tell us what you need reviewed
Name the applications, cloud accounts or data in question, and any deadline. We reply within two business days.