starred/netbox
1
0
Fork 0
mirror of https://github.com/netbox-community/netbox.git synced 2026-01-11 21:10:29 +01:00
Code Issues 273 Packages Projects Releases 10 Wiki Activity

FR - Separate permission for Import / Export options - gdpr #7647

New Issue
Closed
opened 2025-12-29 20:26:25 +01:00 by adam · 4 comments
adam commented 2025-12-29 20:26:25 +01:00
Owner
Copy Link

Originally created by @ITJamie on GitHub (Feb 16, 2023).

NetBox version

v3.4.4

Feature type

Change to existing functionality

Proposed functionality

Right now any user with add or view can access the import / export options on object lists.

I would like to propose additional actions (similar to "run" for scripts) for import/export functionality.

Only those with those actions would be allowed import or export

Use case

imports: We have had some folks with the best of intentions mess up an import adding bad data that needed to be cleaned up. being able to limit who can run imports / exports (per object type) would be a great help

exports: we don't want data to be exportable on certain views (tenants / contacts) as this creates a list of data that has customer contact information and potentially PII in some tenants notes. Under GDPR rules we do not want users exporting certain data to spreadsheets as thats a potential loss of data control.

Database changes

No response

External dependencies

No response

Originally created by @ITJamie on GitHub (Feb 16, 2023). ### NetBox version v3.4.4 ### Feature type Change to existing functionality ### Proposed functionality Right now any user with add or view can access the import / export options on object lists. I would like to propose additional actions (similar to "run" for scripts) for import/export functionality. Only those with those actions would be allowed import or export ### Use case imports: We have had some folks with the best of intentions mess up an import adding bad data that needed to be cleaned up. being able to limit who can run imports / exports (per object type) would be a great help exports: we don't want data to be exportable on certain views (tenants / contacts) as this creates a list of data that has customer contact information and potentially PII in some tenants notes. Under GDPR rules we do not want users exporting certain data to spreadsheets as thats a potential loss of data control. ### Database changes _No response_ ### External dependencies _No response_
adam added the type: feature label 2025-12-29 20:26:25 +01:00
adam closed this issue 2025-12-29 20:26:25 +01:00
adam commented 2025-12-29 20:26:25 +01:00
Author
Owner
Copy Link

@kkthxbye-code commented on GitHub (Feb 16, 2023):

exports: we don't want data to be exportable on certain views (tenants / contacts) as this creates a list of data that has customer contact information and potentially PII in some tenants notes. Under GDPR rules we do not want users exporting certain data to spreadsheets as thats a potential loss of data control.

I'm not sure I agree that the data format is at all relevant to GDPR rules. The data can still be copy/pasted straight from the browser or exported via. the API. Can you link any GDPR resources that states that exporting as csv is different than exposing the data in the browser or via. API?

@kkthxbye-code commented on GitHub (Feb 16, 2023): > exports: we don't want data to be exportable on certain views (tenants / contacts) as this creates a list of data that has customer contact information and potentially PII in some tenants notes. Under GDPR rules we do not want users exporting certain data to spreadsheets as thats a potential loss of data control. I'm not sure I agree that the data format is at all relevant to GDPR rules. The data can still be copy/pasted straight from the browser or exported via. the API. Can you link any GDPR resources that states that exporting as csv is different than exposing the data in the browser or via. API?
adam commented 2025-12-29 20:26:26 +01:00
Author
Owner
Copy Link

@ITJamie commented on GitHub (Feb 16, 2023):

exports: we don't want data to be exportable on certain views (tenants / contacts) as this creates a list of data that has customer contact information and potentially PII in some tenants notes. Under GDPR rules we do not want users exporting certain data to spreadsheets as thats a potential loss of data control.

I'm not sure I agree that the data format is at all relevant to GDPR rules. The data can still be copy/pasted straight from the browser or exported via. the API. Can you link any GDPR resources that states that exporting as csv is different than exposing the data in the browser or via. API?

Its come up as part of an audit that a large amount of data can be extracted by easily by folks who do not need to be able to export data as part of their jobs

@ITJamie commented on GitHub (Feb 16, 2023): > > exports: we don't want data to be exportable on certain views (tenants / contacts) as this creates a list of data that has customer contact information and potentially PII in some tenants notes. Under GDPR rules we do not want users exporting certain data to spreadsheets as thats a potential loss of data control. > > I'm not sure I agree that the data format is at all relevant to GDPR rules. The data can still be copy/pasted straight from the browser or exported via. the API. Can you link any GDPR resources that states that exporting as csv is different than exposing the data in the browser or via. API? Its come up as part of an audit that a large amount of data can be extracted by easily by folks who do not need to be able to export data as part of their jobs
adam commented 2025-12-29 20:26:26 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Feb 16, 2023):

Its come up as part of an audit that a large amount of data can be extracted by easily by folks who do not need to be able to export data as part of their jobs

Any user with permission to access that data can easily extract that data (with varying degrees of ease). Even if you limited users to the web UI, with a bit of effort data exfiltration can be automated via screen scraping.

If you need to limit access from certain users to certain data, I suggest leveraging NetBox's object-based permissions to do so.

@jeremystretch commented on GitHub (Feb 16, 2023): > Its come up as part of an audit that a large amount of data can be extracted by easily by folks who do not need to be able to export data as part of their jobs Any user with permission to access that data can easily extract that data (with varying degrees of ease). Even if you limited users to the web UI, with a bit of effort data exfiltration can be automated via screen scraping. If you need to limit access from certain users to certain data, I suggest leveraging NetBox's [object-based permissions](https://docs.netbox.dev/en/stable/administration/permissions/) to do so.
adam commented 2025-12-29 20:26:26 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Mar 16, 2023):

Closing this out as there's been no further discussion.

@jeremystretch commented on GitHub (Mar 16, 2023): Closing this out as there's been no further discussion.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
beta
breaking change
complexity: high
complexity: low
complexity: medium
needs milestone
netbox
pending closure
plugin candidate
pull-request
Mirrored from GitHub Pull Request
 severity: high
severity: low
severity: medium
status: accepted
status: backlog
status: blocked
status: duplicate
status: needs owner
status: needs triage
status: revisions needed
status: under review
topic: GraphQL
topic: Internationalization
topic: OpenAPI
topic: UI/UX
topic: cabling
topic: event rules
topic: htmx navigation
topic: industrialization
topic: migrations
topic: plugins
topic: scripts
topic: templating
topic: testing
type: bug
type: deprecation
type: documentation
type: feature
type: housekeeping
type: translation
No Label type: feature
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
adam
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/netbox#7647
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?