Papers for

enterprise software integrators

Papers whose findings have a practical use for this group, as judged from the abstract. Open a paper to read what it means in practice.

Enforcing database rules with VBA and SQL Server code

On Enforcing Database Constraints Using MS VBA Event Driven Procedures and SQL Server

Abstract: The goal of this paper is to provide a rigorous methodology for enforcing database constraints using MS VBA event-driven procedures for software applications built on top of MS SQL Server databases, in the framework of the software engineering Database Constraint-Driven Design and Development. The original contribution is a pseudo-code algorithm for assisting developers in this process. We exemplify the results of using it with some VBA code examples taken from a genealogy database software application designed and developed using this methodology. Consequently, it enforces all the database constraints -be they relational or not- which govern this sub-universe of discourse, thus guaranteeing the highest possible quality of its managed data. We also show that the proposed algorithm works fine not only for other relational database management systems, but even with NoSQL platform backends, and that the modifications needed to adapt it to other similar SQL embedding frontend platforms are minimal.

Wed 30 SeptDatabases
The gist
Many software programs need to keep their data accurate by following strict rules called constraints. This paper explains how to use Microsoft VBA code inside applications to automatically enforce those data rules when working with SQL Server databases. The authors provide a clear step-by-step method and example code from a family tree database to show how this enforcement works. They also demonstrate that their approach can be adapted easily for other database systems, including some that aren’t strictly relational.
Open → 2610.00633v1

Common registry improves sharing of cybersecurity playbook integrations

CCR: Towards a Common, Quality-Gated CACAO Integrations Registry for European Cybersecurity Automation

Abstract: Standardised, machine-readable cybersecurity playbooks provide a basis for portable, shareable, and reusable incident-response logic. OASIS CACAO provides a vendor-neutral representation for such playbooks, but not the product-specific integration artefacts needed to invoke external products and services. We introduce the Common CACAO Registry (CCR), an open, provenance-aware registry of CACAO HTTP-API connector envelopes. Each envelope captures an API operation's command, inputs, target, authentication-related information, provenance, validation evidence, and maturity metadata. CCR is \emph{quality-gated}, with acceptance requiring both CACAO v2 schema validity and a mean back-validation score of at least 0.8 against the source OpenAPI operation, while a six-level maturity model records progressively stronger evidence and distinguishes gate acceptance from operational readiness. To seed CCR, we develop a hybrid OpenAPI-to-CACAO pipeline. Deterministic code extracts source-derived interface facts, generates identifiers, wires cross-references, and validates structure, while a constrained LLM provides bounded semantic enrichment, including action naming, authentication interpretation, and CACAO activity annotation. Evaluation across eight security APIs yields 713 CACAO-schema-valid envelopes with a mean back-validation score of 91.5\%, of which 675 produce well-formed, dispatchable HTTP requests in a local harness. Comparison with a deterministic rule-based baseline shows that mechanical API structure is preserved more reliably through rule-based translation, while the LLM contributes bounded semantic enrichment, most notably CACAO activity annotation. Together, these results support CCR as reusable integration infrastructure for CACAO action steps and as an initial foundation for a broader common European registry.

Wed 23 SeptCryptography and Security
The gist
Cybersecurity teams use automated playbooks to respond to incidents, but connecting these playbooks to specific products can be tricky. The authors created a shared registry called CCR that holds detailed descriptions of how to connect playbook steps to different security tools using standard web APIs. They combined automatic extraction of API details with some help from a language model to make this work more accurate and useful. Their evaluation showed the registry contents were high quality and could be reliably used to send commands to actual security products.
Open → 2609.27567v1