The ckanext-userprivs extension enhances CKAN by enabling the assignment of multiple privileges to individual users. Instead of being limited to a fixed set of roles with predefined permissions, this extension provides a more granular and flexible approach to managing user access and capabilities within a CKAN instance. This makes it easier to tailor user permissions to specific needs, promoting a more secure and efficient data management environment. Key Features: Multiple User Privileges: Allows administrators to assign multiple distinct privileges to individual users, providing a more fine-grained control over user permissions compared to traditional role-based access control. Enhanced Access Control: Improves the security and flexibility of CKAN by allowing for precise configuration of what actions each user is permitted to perform within the system. Privilege-Based Permissions: Implements permission checks based on assigned privileges rather than fixed roles, enabling a more adaptable approach to access management. Technical Integration: While the readme doesn't detail specific integration mechanisms, it's reasonable to assume that the extension likely integrates with CKAN's existing user management and authorization framework via plugins or middleware layers. It likely hooks into CKAN's permission checking system to enforce the assigned privileges. Further configuration within CKAN's settings is anticipated to assign and manage privileges for users. Installation of the extension would also be required for the privilege functionality to be granted. Benefits & Impact: By enabling multiple user privileges, ckanext-userprivs offers increased flexibility in managing user access, helping administrators to create more tailored and secure data management environments. This can be particularly beneficial for organizations with complex data governance requirements where precise control over user permissions is essential, making sure that users only have access to the resources and actions they require, enhancing the security and promoting responsibility by limiting liability.

This dataset contains 18,850 normal android application packages and 10,000 malware android packages which are used to identify the behaviour of malware application on permission they need at run-time.

Access Control Market size was valued to be USD 83.22 Billion in the year 2024 and it is expected to reach USD 134.47 Billion in 2031, at a CAGR of 6.82 % over the forecast period of 2024 to 2031.

Access Control Market: Definition/ Overview

Access control is the process of restricting or providing access to resources, systems, or physical regions using predetermined rules and permissions. It is a security mechanism designed to ensure that only authorized individuals or entities have access to certain assets or locations, while unauthorized users are barred from doing so. In information technology and cybersecurity, access control typically includes mechanisms such as passwords, biometric authentication, access cards, and encryption to verify users' identities and regulate their access to digital resources such as files, databases, networks, and apps. Access control systems frequently incorporate authentication, authorization, and auditing components to manage user identities, set access privileges, and track user activity for security and compliance reasons. The future scope of access control systems is poised for tremendous expansion and innovation as technology advances. Biometric advancements, such as facial recognition and iris scanning, have the potential to improve access control security and convenience while simultaneously addressing privacy and data protection issues. Furthermore, the application of artificial intelligence and machine learning algorithms allows access control systems to dynamically adapt to changing threats and user behaviour, offering proactive security measures.

This research examines how various factors, such as the degree of e-privacy concerns and control over data access permissions, can influence a user's intention to install a smartphone app. We conducted two survey-based experiments with 441 participants. In each experiment, we manipulated the degree of control over the number and type of data access permissions granted to different fictional apps. In Study 1, participants were informed about the set of permissions the apps required. In Study 2, participants indicated which individual permissions they were willing to grant to the apps. In both experiments, we assessed the level of e-privacy concerns, perceived app importance, and the intention to install the apps. The results suggest that the type of app plays a central role in determining both the perceived benefit of installing the app and the level of e-privacy concerns. The intention to install an app is more strongly associated with perceived app importance than with e-privacy concerns (especially when app importance is high, and users have explicit control over which specific data access permissions they want to grant). The implications of these results are discussed regarding psychological factors involved in app installation decision-making process and the importance of promoting data protection by design.

Permitted mineral sites

This dataset reports on the number of active cardholders in the Timberland Regional Library District, a five-county rural library district serving Thurston, Lewis, Mason, Pacific, and Grays Harbor counties. It includes a count of cardholders by each library location and card profile type. Card profiles set library privileges for loan periods, limits on the number of items borrowed or requested, and access to digital materials, public computers, and other library resources.

This dataset is a result of my research production in machine learning and android security. The data were obtained by a process that consisted to create a binary vector of permissions used for each application analyzed {1=used, 0=no used}. Moreover, the samples of malware/benign were devided by "Type"; 1 malware and 0 non-malware.

One important topic to work is to create a good set of malware, because it is difficult to find one updated and with a research work to support it .

If your papers or other works use our dataset, please cite our COLCOM 2016 paper as follows. Urcuqui, C., & Navarro, A. (2016, April). Machine learning classifiers for android malware analysis. In Communications and Computing (COLCOM), 2016 IEEE Colombian Conference on (pp. 1-6). IEEE.

If you need an article in english, you can download another of my works: Urcuqui, Christian., & Navarro, Andres. (2016). Framework for malware analysis in Android. Sistemas & Telemática, 14(37), 45-56.

ccurcuqui@icesi.edu.co

Annotated Android App Descriptions 'Enhancing Fidelity of Description in Android Apps with Category-based Common Permissions'.- common_permission.json: It contains a set of common permissions for each category in Play Store.- clean_annotated_dataset.csv: original annotated dataset covers 26 permissions in 10 groups.- augmented_dataset.csv: We augmented the annotated dataset by Thesaurus and backtranslation techniques.- API_mappings.csv: The mappings between Android permissions and corresponding APIs for 26 permissions (API level 16-28).Please check the paper to get more information.

(:unav)...........................................

This dataset reports on the number of new cardholders registered in the Timberland Regional Library District, a five-county rural library district serving Thurston, Lewis, Mason, Pacific, and Grays Harbor counties. It includes a count of cardholders by each library location, card profile type, and date registered. Card profiles set library privileges for loan periods, limits on the number of items borrowed or requested, and access to digital materials, public computers, and other library resources.

This dataset reports on the number of registered cardholders in the Timberland Regional Library District, a five-county rural library district serving Thurston, Lewis, Mason, Pacific, and Grays Harbor counties. It includes a count of cardholders with activity in the previous 3 years, by each library location, card profile type, and year of last activity. Card profiles set library privileges for loan periods, limits on the number of items borrowed or requested, and access to digital materials, public computers, and other library resources.

This set contains data on the issued permissions for violation of objects of improvement.

The Resourceauthorizer extension for CKAN introduces resource-level access control, enhancing the platform's existing dataset-level permission management. This extension allows administrators to specify which users or organizations can access individual resources within a dataset, enabling more granular control over data visibility. By providing this functionality, Resourceauthorizer helps organizations manage sensitive data and ensure that access is granted only to authorized parties. Key Features: Resource-Level Access Control: Grants the ability to define access permissions for individual resources within a dataset, offering finer-grained control than dataset-level permissions alone. User-Specific Permissions: Allows setting access permissions for specific users, enabling direct control over who can access a resource. Organization-Based Permissions: Facilitates the assignment of access permissions to entire organizations, streamlining permission management for groups of users. All members of the specified organization will be affected. Permission Precedence: Prioritizes user-level access rules over organization-level rules when both exist. The extension always uses access permission at user-level as the final decision. Metadata Access: Specifies that allowing user/organization to access a resource will enable the access of the dataset metadata for that user/organization. Use Cases (Inferred): Controlled Data Sharing: Organizations can use this extension to selectively share specific resources within a dataset with partners or external stakeholders while keeping other resources private. Internal Data Governance: Departments within an organization can restrict access to certain resources to only authorized personnel, ensuring data security and compliance with internal policies. Technical Integration: To install the extension, the readme specifies, activating a CKAN virtual environment, installing the extension's Python package, adding resourceauthorizer to the ckan.plugins setting in the CKAN configuration file, updating the database with the necessary tables and reindexing the CKAN metadata in solr. A CKAN restart is necessary to apply the changes. It was developed and tested under CKAN-2.7.3. Benefits & Impact: By extending CKAN's access control capabilities to the resource level, Resourceauthorizer enhances data security and privacy. It enables organizations to manage access to sensitive data with greater precision, ensuring that only authorized users or organizations can access specific resources within a dataset. The extension's support for both user and organization-based permissions simplifies access management and caters to different organizational structures and data sharing requirements.

In the topic of management areas, reporting units are provided in an excerpt from the Berechtams database all valid mining authorisations according to §3 Bundesberggesetz (BBergG) of 13 August 1980 (BGBl. I p. 1310) as amended. The data set contains searches and areas with mining authorisations, information on the type of authorisation according to the Federal Mining Act and the environmental sector. The geodata of the mining authorisations do not have a legally binding character in the sense of information from the legal entity issued by the authorities.

The configpermission extension for CKAN provides a web-based interface for system administrators to manage CKAN permissions and create new roles within organizations. This enhancement offers a user-friendly approach to permission management, allowing administrators to configure who can perform specific actions within CKAN without directly modifying code or configuration files. The primary aim is to simplify the process of assigning and modifying permissions, and creating new organizational roles, thereby easing the administrative overhead of managing a CKAN instance. Key Features: Web-Based Permission Management: Facilitates the configuration of CKAN permissions through a dedicated web interface available to sysadmins, eliminating the need for direct configuration file editing. Organization Role Creation: Empowers administrators to define custom roles within organizations, providing granular control over user access and capabilities specific to organizational contexts. Configurable Permission Settings: Allows administrators to select which permissions will be manageable through the web interface by specifying them in the CKAN configuration file. Streamlined Permission Assignment: Intended to provide a more straightforward method for assigning and modifying permissions compared to manual configuration adjustments. Database Initialization: Requires a database initialization step after installation to properly set up the extension's data structures. Default Data Creation: Includes a step to create default data necessary for the extension to function as expected. Technical Integration: The configpermission extension integrates with CKAN by adding a section, presumably on the sysadmin page, where the permission configuration can take place. The CKAN configuration file (production.ini) needs to be modified to load the plugin and to specify the permissions that should be manageable through this web UI. Benefits & Impact: By offering a web interface for managing permissions and creating organizational roles, the configpermission extension aims to reduce the complexity associated with CKAN administration. This enables administrators to rapidly adapt permission settings to evolving organizational needs, ultimately improving the usability and security of the CKAN instance. It likely reduces the administrative effort needed when new users join or organizational structures change.

This database was generated from the analysis of 255K commits from 324 Android apps by Sniffer.It contains the full history of 180K Android code smells.This is a PostgreSQL database, use the following commands to access it:$ sudo su - postgres$ psqlpostgres=> CREATE DATABASE tracker;postgres=> CREATE USER tracker WITH PASSWORD 'tracker';postgres=> GRANT ALL PRIVILEGES ON DATABASE tracker to tracker;$ psql postgres://localhost:5432/tracker -U tracker < Database_Sniffer.sql$ psql postgres://localhost:5432/tracker -U trackertracker=> set SEARCH_PATH to tracker;

The ckanext-collaborator_orgs extension enhances CKAN's collaborative features by extending collaborator functionality to user organizations. It enables organization members to be granted edit or read-only access to private datasets, streamlining data access management within organizations using CKAN. The extension focuses on extending existing collaborator features rather than introducing new major functionality. Key Features: Organization-Based Access Control: Allows administrators to grant edit or read-only permissions to entire organizations for private datasets, simplifying the management of access rights for groups of users. Extended Collaborator Functionality: Builds upon CKAN's existing collaborator model, providing a more scalable and manageable way to grant permissions to larger teams or departments. Configuration-Free Operation: Operates without requiring specific configuration settings, which simplifies initial setup and reduces the overhead of managing additional parameters. Integration with CKAN: This extension integrates with CKAN by adding functionality to the collaborator model. It likely leverages CKAN's plugin system and existing access control mechanisms to enable organization-level permissions for private datasets, and requires initialization of database tables. Benefits & Impact: By using the ckanext-collaborator_orgs extension, organizations using CKAN can simplify the administration of permissions for private datasets. This enhancement streamlines workflows and permission updates for large teams and allows organization users to directly manage organization-level access, which reduces the burden on administrators and promotes more efficient data sharing within CKAN installations by using a systematic approach.

Setting up lab privileges.

Description: ======================================= This dataset applies to Felling Permission Applications (formerly Felling Licence Applications) received by Scottish Forestry (formerly Forestry Commission Scotland) after 1st January 2012 and administered using Scottish Forestry's Case Management System. ======================================= Anyone wishing to fell trees must ensure that a Felling Permission (formerly Felling Licence) or approval under a grant scheme has been issued by Scottish Forestry before any felling is carried out or that one of the exceptions apply. You normally need to get permission from Scottish Forestry to fell growing trees. This is usually given in a Felling Permission or an approval under a grant scheme. In certain circumstances you may also need special permission from another organisation for any proposed felling. This sometimes applies even if you do not need a Felling Permission. Everyone involved in the felling of trees, whether doing the work or by engaging others, eg. the owner, agent, timber merchant or contractor, must ensure that a Felling Permission or approval under a grant scheme has been issued before any felling is carried out or that one of the exceptions apply. They must also ensure that the work is carried out in accordance with the terms of a Scottish Forestry Felling Permission. If there is no permission, or if the wrong trees are felled, anyone involved can be prosecuted. Do not begin felling until Scottish Forestry have issued a Felling Permission or other approval. Any felling carried out without either a Felling Permission or other approval is an offence, unless it is covered by an exception. Attributes: CASE_REFERENCE : Case reference number NAME_OF_PROPERTY : Property name STATUS : The current status of the application FELL_OPERATION_TYPE : The type of felling operation FELL_AREA : The applicants estimated area of felling. Applies to the specific operation FELL_VOLUME : The estimated volume from felling in cubic meters. Applies to the specific operation NEAREST_TOWN : Nearest town LOCAL_AUTH : Local Authority CONSERVANCY : Conservancy GRID_REF : National Grid Reference REGISTERED : Date Registered START_OF_PUBLIC_CONSULTATION : Public consultation start date END_OF_PUBLIC_CONSULTATION : Public consultation end date DECISION_ISSUED_ON : Date decision issued LICENCE_EXPIRY_DATE : Date licence expires RESTOCK_DUE_DATE : The date of any restocking requirements DATE_VALIDATED : The date of the licence decision DATE_CLOSED : The date the licence closed FELLING_OPERATION_SUMMARY_ID : Felling operation code