35 results found
-
Ability to store assessment documentation in the customer's cloud environment
An option to configure an assessment's documentation (workpapers, audit evidence) to reside in the client's cloud hosting provider instead of in MyCSF's default storage location, such as:
- Client's box.com
- Client's S3 bucket
- Client's Google drive
- Client's SharePointThis would require the client to grant the MyCSF application access into a specific area in their cloud environment. This would be very beneficial to customers who don't want to allow assessment documentation to leave their controlled environments.
This would also require MyCSF to store assessment documentation in a folder structure that can be navigated with something like Windows…
40 votes -
Option to NOT include attachments from previous certification in the next assessment object
When creating a new assessment object AFTER already having been certified (i.e., in a re-certification scenario), MyCSF should have an option to include or NOT include the documentation linkages present in the previous assessment object.
26 votes -
Search all attached documents for keyword(s)
MyCSF should allow users to perform a keyword search throughout all attached documents. While this obviously wont search screenshots and non-OCR'd PDFs, the ability to do a mass search of all uploaded documents in one run would be valuable.
21 votes -
Ability to sort documents list
The general documents view should allow the user to sort the documents by date uploaded, by document title, and by document description.
19 votes -
Give External Assessors the ability to unlink documents linked by the client
It would be helpful if external assessors could remove files linked by the assessed client in the portal. This would help reduce the chance that superflous documentation is linked or incorrect versions of documnts are attached to requirement statements.
17 votes -
Give assessors an easy way to "reject" evidence linked to a requirement statement by the assessed entity
If a document was identified as associated with a requirement statement or requirement statement's PRISMA attribute(s), the assessor should be given an easy way to flag items as irrelevant to the PRISMA attribute and to the requirement statement. Its common for the customer to link files that may be related to other requirements but not necessarily to the requirement statement at hand.
16 votes -
Automated Sample Test Plan
The process by which we as assessors take to determine what controls need sample testing is time-consuming and tedious. Since all the information is in MyCSF - why not make it much easier for us and develop the test plan automatically based on scope and factors? At least give us a list of which controls need testing and we can place that in the excel spreadsheet format.
9 votes -
Ability to automatically associate documents with requirement statements and PRISMA levels during bulk upload using a folder structure
When doing a bulk upload of documents (screenshots, workpapers, etc.) via a compressed zip archive using the bulk upload functionality, users should be able to automatically associate documents with requirement statements and PRISMA levels (e.g., policy) using a defined folder structure within the archive.
The folder structure can be something like this:
-- domain
--- requirement statement ID
---- policy
---- process
---- implemented
---- measured
---- managedDocuments present in these folders would be (a) uploaded, (b) associated with the requirement statement, and (c) tagged to the PRISMA levels
9 votes -
Document Upload Alert
Can the tool be updated to send alerts to assessors with access to the assessment when documents are uploaded?
8 votes -
When viewing the linked documents for a particular Requirement Statement, documents should download with the original file name.
Linked documents, when downloaded from the linked documents pop-up, are first previewed in the new document preview window, and when downloaded, are presented with a guid-style file name instead of the original name.
7 votes -
Include requirement number when searching linked documents through Documents tab.
Right now, there is just the requirement statement and many times, if the document is attached in a domain more than once, it isn't even shown in order, so you have to search all around to find the requirement statement rather than just have the requirement number itself carry over into that Linked Statements Document view and easily searchable.
7 votes -
Document replace functionality should also replace file's name (not just file contents)
The document replace functionality should also replace document's name (not just document's contents). Right now it appears to replace the document contents but leaves the old document name.
7 votes -
[BL] Documentation Request
Capability for Assessors to solicit their Clients to upload evidence into MyCSF for a given Statement.
7 votes -
Related Requirements
suggest related requirements that may be met with an uploaded document.
For example, a policy is loaded to support 00.a. A dropdown or picklist would be populated with other 00.a control requirements.6 votes -
Documents Repository and Linkage
One of the most time consuming tasks in performing assessments is the linkage of documentation. I think it would be helpful if our documentation repository creates a slot for each document. The slot is then mapped in a one to many relationship model to control requirements. The documents are then uploaded to the virtual slot. The big advantage is that documents in the slots can be automatically mapped to any assessment object and if the most recently reviewed version of a policy is uploaded to the slot to replace the old version, the new one automatically mapped as well. This…
6 votes -
Don't overwrite document metadata
When downloading workpapers / documents, MyCSF currently erases the file metadata. For example, when downloading a file the "date created" field gets overwritten to the date the file was downloaded from MyCSF. MyCSF should not mess with any document's metadata at all. I'd like to be able to see the original date created as well as all of the other original metadata associated with the file.
6 votes -
Bulk Deletion
This is especially relevant to cloned assessments in my experience, but it would be nice if MyCSF had a feature to bulk-delete uploaded documents in the "Documents" section.
5 votes -
Save and Close on Document Modal
Please provide an option to both Save and Close the window when linking documents to a requirement statement. Right now, this takes 2 clicks. We have to save the document links before we can close... then we have to close to get back out to the requirement statement to complete our scoring. It's a lot of clicking already to link all the documents. Please take one click away. Thank you!
5 votes -
Copy mapping from evidence items to others.
When uploading evidence for controls often one piece of evidence is used for multiple controls or there are multiple evidence items supporting the same control stage (policy, procedure, implemented). The ability to copy the mapping from one item to another would be a huge time saver.
4 votes -
Ability to upload, access, and edit assessment documentation using something other than the Web interface
MyCSF should support common file handling protocols to manage assessment documentation. This should operate similar to how Web applications such as media servers (Plex, Ombi) and online document repositories (livelink, sharepoint) work... these allow the upload and accessing of files using a alternate protocols such as SAMBA, SCP, and SFTP. Any file and folder changes made using supported protocols are reflected in the Web application front-ends. MyCSF should function in a similar fashion.
If this existed, users wouldn't have to upload each and every file using our Web front-end nor would they have to manually associate each artifact to the…
4 votes
- Don't see your idea?