Policy - Revision history

Nathanrwells: /* Classified, PII/HIPAA, CUI, and/or export controlled data */

2025-02-27T20:37:37Z

Classified, PII/HIPAA, CUI, and/or export controlled data

← Older revision		Revision as of 15:37, 27 February 2025
Line 13:		Line 13:
	[[wikipedia:Controlled Unclassified Information\|CUI]],		[[wikipedia:Controlled Unclassified Information\|CUI]],
	[[wikipedia:Personally_identifiable_information\|PII]], or [[wikipedia:Health_Insurance_Portability_and_Accountability_Act\|HIPAA]].		[[wikipedia:Personally_identifiable_information\|PII]], or [[wikipedia:Health_Insurance_Portability_and_Accountability_Act\|HIPAA]].
	For this type of data we suggest ~~the~~ contacting the K-State Office of Compliance for assistance: [https://www.k-state.edu/comply/ K-State Compliance Office].		For this type of data we suggest contacting the K-State Office of Compliance for assistance: [https://www.k-state.edu/comply/ K-State Compliance Office].
	[[wikipedia:Export_Administration_Regulations\|Export controlled]] data and computation may occur on Beocat with the concurrence		[[wikipedia:Export_Administration_Regulations\|Export controlled]] data and computation may occur on Beocat with the concurrence
	of the appropriate KSU personnel, generally a collaboration between the researchers, Beocat staff, the Compliance Office and CISO		of the appropriate KSU personnel, generally a collaboration between the researchers, Beocat staff, the Compliance Office and CISO

Nathanrwells: /* Classified, PII/HIPAA, CUI, and/or export controlled data */

2025-02-27T20:37:15Z

Classified, PII/HIPAA, CUI, and/or export controlled data

← Older revision		Revision as of 15:37, 27 February 2025
Line 13:		Line 13:
	[[wikipedia:Controlled Unclassified Information\|CUI]],		[[wikipedia:Controlled Unclassified Information\|CUI]],
	[[wikipedia:Personally_identifiable_information\|PII]], or [[wikipedia:Health_Insurance_Portability_and_Accountability_Act\|HIPAA]].		[[wikipedia:Personally_identifiable_information\|PII]], or [[wikipedia:Health_Insurance_Portability_and_Accountability_Act\|HIPAA]].
	For this type of data we suggest the [https://www.k-state.edu/comply/~~cui/research-security.html~~ K-State ~~Research Information Security Enclave (RISE)~~].		For this type of data we suggest the contacting the K-State Office of Compliance for assistance: [https://www.k-state.edu/comply/ K-State Compliance Office].
	[[wikipedia:Export_Administration_Regulations\|Export controlled]] data and computation may occur on Beocat with the concurrence		[[wikipedia:Export_Administration_Regulations\|Export controlled]] data and computation may occur on Beocat with the concurrence
	of the appropriate KSU personnel, generally a collaboration between the researchers, Beocat staff, the Compliance Office and CISO		of the appropriate KSU personnel, generally a collaboration between the researchers, Beocat staff, the Compliance Office and CISO

Nathanrwells at 16:11, 4 October 2024

2024-10-04T16:11:57Z

← Older revision		Revision as of 11:11, 4 October 2024
Line 69:		Line 69:
	##; NOTE : This requirement can be waived for tenure track (but not yet tenured) faculty if the faculty member has a compelling tenure-related interest in, for example, producing single-author publications.		##; NOTE : This requirement can be waived for tenure track (but not yet tenured) faculty if the faculty member has a compelling tenure-related interest in, for example, producing single-author publications.
	## If the conditions above don't apply, then the Beocat staff member should be acknowledged by name and job title in the Acknowledgements section of the paper.		## If the conditions above don't apply, then the Beocat staff member should be acknowledged by name and job title in the Acknowledgements section of the paper.
	##; For example : Beocat Director Daniel Andresen and Beocat Systems Administrator ~~Adam Tygart~~ provided valuable technical expertise.		##; For example : Beocat Director Daniel Andresen and Beocat Systems Administrator Nathan Wells provided valuable technical expertise.
	# A citation for your publication should be added to our [[PapersAndGrants\|papers and grants page]].		# A citation for your publication should be added to our [[PapersAndGrants\|papers and grants page]].

Mozes: /* Administrative access to home, bulk and scratch directories */

2023-08-09T19:54:52Z

Administrative access to home, bulk and scratch directories

← Older revision		Revision as of 14:54, 9 August 2023
Line 54:		Line 54:
	we will mark the account for archival, and remove your ability to login. If you should need the account again, please fill out our [https://account.beocat.ksu.edu/user account request form.]		we will mark the account for archival, and remove your ability to login. If you should need the account again, please fill out our [https://account.beocat.ksu.edu/user account request form.]

	== Administrative access to home, bulk and ~~scratch~~ directories ==		== Administrative access to home, bulk and fastscratch directories ==
	Beocat support staff have the need, from time to time, to access information contained within the directories of other users, for support purposes. To that end, there is an access control list that gives them read access to user home, bulk, and fastscratch directories.		Beocat support staff have the need, from time to time, to access information contained within the directories of other users, for support purposes. To that end, there is an access control list that gives them read access to user home, bulk, and fastscratch directories.

Mozes: /* Administrative access to home, bulk and scratch directories */

2023-08-09T19:54:33Z

Administrative access to home, bulk and scratch directories

← Older revision		Revision as of 14:54, 9 August 2023
Line 55:		Line 55:

	== Administrative access to home, bulk and scratch directories ==		== Administrative access to home, bulk and scratch directories ==
	Beocat support staff have the need, from time to time, to access information contained within the directories of other users, for support purposes. To that end, there is an access control list that gives them read access to user home, bulk, and ~~scratch~~ directories.		Beocat support staff have the need, from time to time, to access information contained within the directories of other users, for support purposes. To that end, there is an access control list that gives them read access to user home, bulk, and fastscratch directories.

	== Directory Permissions ==		== Directory Permissions ==

Dan: /* Classified, PII/HIPAA, CUI, and/or export controlled data */

2023-04-21T21:07:21Z

Classified, PII/HIPAA, CUI, and/or export controlled data

← Older revision		Revision as of 16:07, 21 April 2023
Line 12:		Line 12:
	Beocat is not equipped to store and/or compute on [[wikipedia:Classified_information\|Classified]],		Beocat is not equipped to store and/or compute on [[wikipedia:Classified_information\|Classified]],
	[[wikipedia:Controlled Unclassified Information\|CUI]],		[[wikipedia:Controlled Unclassified Information\|CUI]],
	[[wikipedia:Personally_identifiable_information\|PII]], [[wikipedia:Health_Insurance_Portability_and_Accountability_Act\|HIPAA]] ~~or [[wikipedia:Export_Administration_Regulations\|export controlled]] data~~.		[[wikipedia:Personally_identifiable_information\|PII]], or [[wikipedia:Health_Insurance_Portability_and_Accountability_Act\|HIPAA]].
	For this type of data we suggest the [https://www.k-state.edu/comply/cui/research-security.html K-State Research Information Security Enclave (RISE)].		For this type of data we suggest the [https://www.k-state.edu/comply/cui/research-security.html K-State Research Information Security Enclave (RISE)].
			[[wikipedia:Export_Administration_Regulations\|Export controlled]] data and computation may occur on Beocat with the concurrence
			of the appropriate KSU personnel, generally a collaboration between the researchers, Beocat staff, the Compliance Office and CISO
			to determine appropriate safeguards are in place prior to the start of Beocat usage.

	== Access ==		== Access ==

Mozes: /* Account deactivation */

2023-01-10T15:58:40Z

Account deactivation

← Older revision		Revision as of 10:58, 10 January 2023
Line 46:		Line 46:
	* lack of a K-State sponsor if you are not a K-State student or employee		* lack of a K-State sponsor if you are not a K-State student or employee
	** upon the transition from K-State student or employee to not being a K-State student or employee your account will be automatically deactivated. If you still have need of your account you will need to reapply.		** upon the transition from K-State student or employee to not being a K-State student or employee your account will be automatically deactivated. If you still have need of your account you will need to reapply.
	** unfortunately, it would seem this gets triggered a week or two before the new semester if student hasn't enrolled for the new semester yet.		** unfortunately, it would seem this gets triggered a week or two before the new semester if the student hasn't enrolled for the new semester yet.
	* failed to follow up on the annual renewal process		* failed to follow up on the annual renewal process

Mozes: /* Account deactivation */

2023-01-10T00:58:42Z

Account deactivation

← Older revision		Revision as of 19:58, 9 January 2023
Line 46:		Line 46:
	* lack of a K-State sponsor if you are not a K-State student or employee		* lack of a K-State sponsor if you are not a K-State student or employee
	** upon the transition from K-State student or employee to not being a K-State student or employee your account will be automatically deactivated. If you still have need of your account you will need to reapply.		** upon the transition from K-State student or employee to not being a K-State student or employee your account will be automatically deactivated. If you still have need of your account you will need to reapply.
	** unfortunately, it would seem this gets triggered a week or two before the new semester if ~~students haven~~'t enrolled for the new semester yet.		** unfortunately, it would seem this gets triggered a week or two before the new semester if student hasn't enrolled for the new semester yet.
	* failed to follow up on the annual renewal process		* failed to follow up on the annual renewal process

Mozes: /* Account deactivation */

2023-01-10T00:58:24Z

Account deactivation

← Older revision		Revision as of 19:58, 9 January 2023
Line 46:		Line 46:
	* lack of a K-State sponsor if you are not a K-State student or employee		* lack of a K-State sponsor if you are not a K-State student or employee
	** upon the transition from K-State student or employee to not being a K-State student or employee your account will be automatically deactivated. If you still have need of your account you will need to reapply.		** upon the transition from K-State student or employee to not being a K-State student or employee your account will be automatically deactivated. If you still have need of your account you will need to reapply.
	*** unfortunately, it would seem this gets triggered a week or two before the new semester if students haven't enrolled for the new semester yet.		** unfortunately, it would seem this gets triggered a week or two before the new semester if students haven't enrolled for the new semester yet.
	* failed to follow up on the annual renewal process		* failed to follow up on the annual renewal process

Mozes: /* Account deactivation */

2023-01-10T00:58:12Z

Account deactivation

← Older revision		Revision as of 19:58, 9 January 2023
Line 46:		Line 46:
	* lack of a K-State sponsor if you are not a K-State student or employee		* lack of a K-State sponsor if you are not a K-State student or employee
	** upon the transition from K-State student or employee to not being a K-State student or employee your account will be automatically deactivated. If you still have need of your account you will need to reapply.		** upon the transition from K-State student or employee to not being a K-State student or employee your account will be automatically deactivated. If you still have need of your account you will need to reapply.
			*** unfortunately, it would seem this gets triggered a week or two before the new semester if students haven't enrolled for the new semester yet.
	* failed to follow up on the annual renewal process		* failed to follow up on the annual renewal process