Built around your environment.
Blackcube Solutions works with Australian businesses to examine the parts of a website that are agreed for testing. This can be useful before a launch, after a substantial change, or when you need a clearer view of an existing site. Testing is authorised in writing and tailored to the website and its hosting arrangements.
What we assess.
The specific checks depend on your systems and the agreed scope. Areas we can discuss include:
Exposed components
Review the agreed website components and publicly accessible services for weaknesses, unnecessary exposure and indications of outdated software.
Login and access controls
Examine how users sign in and whether access boundaries protect the pages and functions included in the assessment.
Information disclosure
Look for configuration details, files or responses that may reveal information beyond what the website intends to share.
Website configuration
Review relevant web security settings and the way the site handles requests within the agreed testing boundaries.
When this assessment can help.
- Before launching a new public website or after changing its CMS, plugins or hosting arrangements.
- When you need to understand exposure around public pages, website logins and the components supporting them.
- When your website provider needs a clearly scoped set of security findings to investigate and address.
Clear scope. Useful conclusions.
A website assessment focuses on the agreed public presence and supporting components. A customer portal with multiple roles, record access and complex workflows may need a web application assessment as well. Payment providers, hosting infrastructure and other third-party systems are included only where the scope and permissions explicitly allow it.
Before testing begins.
Start with the website address, your reasons for testing, and who manages the site and hosting. We agree on included domains, excluded systems, test accounts where needed, and a suitable testing window. Permission from the relevant system owner is required before testing starts.
Findings you can work with.
Receive a report describing identified weaknesses, their potential impact and recommended remediation. The findings are discussed in the context of your business so you can decide what to address first. Follow-up review or retesting can be scoped separately.
From findings to improvements.
Share the relevant findings with the person who owns the website, its hosting or its components. Agree on responsibility for each change and discuss any impact on the site's operation. After remediation, a separate follow-up can check selected fixes against the original finding; substantial new functionality may require a fresh scope.
Common questions.
Can you assess a website built by another provider?
Yes, subject to an agreed scope and permission from the relevant system owners. Hosting and third-party platform policies must be understood before testing begins.
Does a website assessment guarantee the site is secure?
No. An assessment examines an agreed scope at a particular time. It can identify weaknesses and guide remediation, but cannot guarantee the absence of all vulnerabilities.