China
Africa
Explore chapters and articles related to this topic
Data Security and Privacy
Published in Bhavani Thuraisngham, Murat Kantarcioglu, Latifur Khan, Secure Data Science, 2022
Bhavani Thuraisngham, Murat Kantarcioglu, Latifur Khan
Typically, the database administrator (DBA) is responsible for updating, say, the metadata, the index and access methods, and also ensuring that the access control rules are properly enforced. The System Security Officer (SSO) may also have a role. That is, the DBA and SSO may share the duties between them. The security-related issues might be the responsibility of the SSO while the data-related issues might be the responsibility of the DBA. Some other administration policies being considered include assigning caretakers. Usually owners have control of the data that they create and may manage the data for its duration. In some cases, owners may not be available to manage the data, in which case they may assign caretakers (i.e., custodians).
Prioritization of Assets and Establishing a Plan for Resilient Change
Published in Dan Shoemaker, Anne Kohnke, Ken Sigler, How to Build a Cyber-Resilient Organization, 2018
Shoemaker Dan, Kohnke Anne, Sigler Ken
Baseline competencies may be as detailed as necessary in order to describe its required set of skills and are shown in Figure 4.7. This generally includes several layers of information, including role or position (security administrator, network administrator, chief information officer (CIO), analyst, programmer, etc.);skills (C# programming, Python, structured query language (SQL) Server database administrator (DBA), security risk assessment and mitigation, etc.);certifications (CISSP, C|EH, CCNA, MCSE, CAP. A+, etc.);aptitudes and job requirements (able to work long hours, travel, or be on call).
AnyEntity Stable Design Pattern
Published in Mohamed E. Fayad, Stable Design Patterns for Software and Systems, 2017
In the above diagram, AnyParty can have many roles such as Database Administrator, HealthCare provider, or a Database User. A person (AnyParty) who is a Database Administrator can also be a Database User. In the above scenario, we also see that the same person at different times can play various roles. Therefore, if we need to represent the same person for different roles, then we need to create multiple instances that can represent different changes for different roles. In order to avoid the above problem, delegation pattern can be used. Delegation pattern uses delegation to represent persons for different roles. The diagram given below explains how a delegation pattern can be used to delegate various roles to different objects at run time.
Explaining Digital Technology: Digital Artifact Delineation and Coalescence
Published in Journal of Computer Information Systems, 2023
It is possible in advanced digital technologies for different users to interact with the same system using distinct interaction layers or application programming interfaces (APIs). In order to better understand this point, we will use an example involving a DBMS. An end-user is able to interact with the DBMS through the use of a query interface tool such as TOAD or Query analyzer. On the other hand, a database administrator (DBA) is able to interact with the system through the use of the database management console. Therefore, the DBMS interaction zone for the end-user is the query interface tool, and everything else in the DBMS system can be considered to be the non-interaction zone. On the other hand, the interaction zone for the DBA when the DBA is performing regular database maintenance is the management console, and everything else in the DBMS is the non-interaction zone for the DBA at that particular time.
High-capacity separable reversible data-Hiding method in encrypted images based on block-level encryption and Huffman compression coding
Published in Connection Science, 2021
Kai-Meng Chen, Chin-Chen Chang
With the development of cloud computing and Internet of Things, data processing in the encryption domain becomes more and more important (Chang & Li, 2019; Kui et al., 2020; Xiao et al., 2020). Reversible data hiding in encrypted images (RDHEI) is receiving increased attention. RDHEI is the technology that is used to embed data directly in encrypted images without decryption or knowledge of the content of the images. RDHEI is highly useful for the application scenarios in which the third party wants to perform data hiding for a specific purpose but has no access to the contents of the images for privacy or other reasons. For example, in a hospital, to protect the patients’ privacy, the medical images are encrypted before being stored in the medical image database, and the database administrator can embed related information directly into the encrypted medical images for data management without knowing the contents of the images.
Requirements of a data storage infrastructure for effective land administration systems: case study of Victoria, Australia
Published in Journal of Spatial Science, 2022
Davood Shojaei, Farshad Badiee, Hamed Olfat, Abbas Rajabifard, Behnam Atazadeh
In addition to these requirements, the following features were also considered according to the business requirements: Collection of parcels must be supported. This is called multi part parcels when not connected parcels such as car park and associated lot exist in a plan.Different geometry types such as curves (arcs) must be supported.In order to respond to spatial queries such as neighbourhood analysis or buffer analysis, the geometry of parcels must be created in a way to indicate the order of points and lines within each parcel. The direction of parcels in the ePlan was considered as clockwise. This convention enables the user to utilise the topology of objects in spatial query and analysis.Natural (irregular) boundaries (e.g. river and creek borders) must be supported. In ePlan files, each irregular boundary is made of numerous middle points between the start and end points. The aim of this rule is to generate an irregular line from these several points.During extraction, transform, and load of the data from ePlans to other database objects, any error must be recorded in the database to be followed up by the database administrator. Error information details must be informative to help the administrator resolve the issue. For instance, if a duplicated plan is being inserted, the database must prevent the insertion of the plan and record an error in the error table.All ePlans inserted into the database must have a minimum bounding box (MBB) to cover their geographic extent. This geometry is created automatically once an ePlan is inserted into the database. It will be used for spatial queries on ePlans based on their coverage area, e.g. drawing a polygon and downloading all parcels from existing ePlans that intersect with that polygon.ePlans may belong to more than one administrative area (i.e. Local Government Area and Parish). In this case, ePlans must be stored in the database with proper link to each administrative area.A mechanism is required to receive ePlan files from the lodgement portal to send them to the database for storage.