Technical Assessment

A company with core business of real estate, construction, tourism, mining and financial investment which head quarter is located in Hong Kong with multiple sites in Mainland China

Size
500+ Employees

Service
Vulnerability Assessment and Penetration Test

Challenge
Organization is getting more concerns in information security as there is a significant increase in cyber security attack nowadays. However, limited review and regular technical assessment in this organization causes the system and network vulnerabilities have been accumulated throughout the years. Given with this scenario and the scale of the technical assessment which has to be conducted across different sites, our technical specialist and pentesters have to put extra effort in evaluating the security and risk level in order to define the baseline security level and controls that are being implemented in the organization. Furthermore, it is also critical to provide practical recommendation as to resolve the issues identified in this technical assessment. 

Solution
Our certified OSCP, OSWP and GPEN conducted network and web application penetration test to simulate hacker’s activities as to prevent external attack. Internal vulnerabilities assessment is also performed to discover the unmanaged asset. Identify the vulnerabilities with technical tools and manual validation with risk level provided.
 
Result
Our security specialists have issued a penetration test and vulnerabilities assessment report on the security findings with different level of severity. Critical vulnerabilities and system deficiencies are identified such as SQL injection, missing security patches and remote code execution are identified through exploitation and privilege escalation that are putting company asset at risk. Technical recommendations and advisories are provided according to the existing industrial standard. Latest security protection methods and tools were also suggested for future improvement.

The technical assessment report including:
 •    Prioritized list of vulnerabilities
 •    Specific information about the vulnerabilities exploited
 •    The risk level of the vulnerabilities
 •    The description and evidence of the vulnerabilities
 •    Potential impact
 •    Technical recommendations

Follow-up
After our assessment and in-depth analysis of the security testing, Ringus has provided a detailed report documenting each security issue with a set of security recommendations (methods and tools) and corrective action plans. Findings walkthrough session is also conducted to ensure our client understand the issues and able to implement those plans accordingly. Ringus has also provided follow-up services for the remediation works to verify that the remedial activities had been successful.
 
Benefit
Our recommendations have provided our client with an up-to-date defense against known vulnerabilities and global hackers, allowing our client to estimate and justify the cost of equipments whenever appropriate in scaling up its security level, providing a continual improvement model. With our comprehensive report, professional recommendations and direct assistance, our client was able to get a realistic idea on the existing security level of their setup. Our work helped the client avert a potential reputational crisis and allowed the company to operate their systems in a confident and secure way.  

More Updates

Further reading

Speed Without the Sprawl

Leveraging OutSystems' rapid development strengths, our team achieves true Agile development, focusing intensely on user requirements. However, requirements are never fixed; they take time to refine within the project's cycle. If a developer simply builds projects based on the initial requirements, it leads to significant rework when those requirements are inevitably revised. This creates serious technical debt that can derail a project's schedule. To combat this, we strictly follow the OutSystems Canvas Design architecture to define each module's usage and content. We generalize logic into foundational modules, optimizing reusability and providing high adaptability when requirements change. This approach allows us to eliminate complicated dependencies—avoiding the deployment nightmares that plague monolithic systems. The Real-World Challenge: "The Spaghetti Monolith" We’ve all seen it. A project starts fast. The "Idea-to-App" time is record-breaking. But as sprints pass and requirements evolve, the "interest rate" on technical debt spikes. Suddenly, changing a simple UI element breaks a core business process because the logic was trapped inside the screen. Deployment becomes a "big bang" event where everything must go live at once because of circular dependencies. In our team, we don't just "code fast"; we architect for resilience. Our Solution: The 4 Layer Canvas Strategy We treat the 4 Layer Canvas not just as a suggestion, but as our structural imperative. Here is how we use it to handle volatile requirements:  Isolating Volatility (End-User Layer): We keep our User Interfaces (UI) and interaction logic in the End-User Layer. This layer is highly volatile—it changes constantly based on user feedback. By isolating it, we can redesign a "Customer Portal" without risking regressions in our core business rules.Stabilizing Business Logic (Core Layer): We abstract our entities and business rules into the Core Layer. This is the backbone of our factory. Whether the data is accessed by a Mobile App, a Web Portal, or a Timer, the validation rules remain consistent. This promotes the "Don't Repeat Yourself" (DRY) principle.Enabling Independent Deployments: By using Service Actions (Weak Dependencies) in our Core layer, we decouple our modules. This allows different squads to deploy changes independently without forcing a factory-wide refresh—a critical enabler for our CI/CD pipelines.The Governor: AI-Driven Architecture How do we ensure we stick to these rules when moving at Agile speeds? We don't just rely on manual code reviews; we use the AI Mentor System. This tool acts as our automated architect. It scans our entire factory to detect architectural violations that humans might miss, such as: Upward References: Preventing foundational libraries from depending on business logic.Side References: Ensuring our End-User apps don't tightly couple with one another.Circular Dependencies: Identifying the "deadly embrace" between modules that locks deployments.The AI Mentor System quantifies this debt, allowing us to pay it down proactively before it hinders our release velocity. Join a Team That Values Architecture In our Taiwan office, we believe that low-code doesn't mean "low-architecture." We are building resilient, composable enterprise ecosystems that can scale. If you are a developer who cares about structural integrity, clean code, and mastering the art of OutSystems architecture, we want to hear from you.