## 4 Overview of LiSEA  
LiSEA, conceived as a safeguarding framework for business processes grounded in the zero-trust paradigm, is structured upon two principal constituents--the embedding client and the operating center--as illustrated in Figure 1.  
To ensure the preservation of the underlying business while demarcating business security concerns from broader application considerations, the embedding client is meticulously structured along the principles of aspect-oriented programming [44]. This design ethos enables the encapsulation of security functionalities within a coherent and cohesive package. Within the dynamics of the business process, the transmission of data between Process A and Process B transpires via API invocations. The embedding client assumes the pivotal role of infusing aspect joints into the business APIs, realizing this integration in a minimally intrusive manner. The aspect joints are dichotomized into pre- and post-intervention points, thereby harmonizing contextual insights and operational interventions during API execution. The pre-intervention point serves to validate the legitimacy of the request intention, while the post-intervention point ascertains the alignment between the response outcome and the identity of the requester.  
The operating center, an indispensable facet of LiSEA, accumulates the corpus of business contextual data collated by the embedding client. This repository is judiciously harnessed to facilitate business security analysis, all of which is choreographed in consonance with configurations delineated by the security department. In essence, the operating center assumes the mantle of processing verification solicitations originating from the embedding client. Subsequent to rigorous analysis and calculated scrutiny of diverse business security scenarios, the operating center dispenses verification responses. Notably,  
Figure 1: Overview of LiSEA.  
the resultant verification records are perpetually preserved, not only serving as fodder for comprehensive business analysis and modeling but also potentially augmenting the repository of application logs.  
The operational agility of the operating center is augmented through the assimilation of third-party security platform capabilities and data, including entities like security operation centers (SOC) [45] and risk control centers. By tapping into the insights of these platforms, the operating center gains a panoramic view of the security landscape, facilitating timely configuration adjustments. Additionally, it operates as an information source and a mechanism for repelling attacks discovered by these third-party security platforms.  
In a holistic context, LiSEA adeptly addresses RQ.1 by ingeniously inculcating access security capabilities via the embedding client without engendering perturbations to the native business processes. This is particularly evident when the embedding client is systematically integrated with each API during the application development phase, thereby rendering all APIs discernible and amenable to operational center management. Consequently, LiSEA effectively surmounts RQ.3, ensuring comprehensive and seamless access of business APIs to security capabilities.