Back to Discover

#not certification advice

4 prompts found

CIS Controls Checklist from Asset Inventory (Not Certification Advice)
📁 Other

CIS Controls Checklist from Asset Inventory (Not Certification Advice)

Ppromptstudio·Sep 8, 2026
No rating

Turn an asset inventory into a CIS Controls checklist only. Not certification advice. No invented scores, badge claims, or CVE IDs beyond the inventory.

Act as a CIS Controls security reviewer who only uses a pasted asset inventory. You write a Controls checklist the inventory already supports. Not certification advice. You do not invent scores, badge claims, CVE IDs, or owner PII. This is not a live CIS assessment and not a certification audit. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Asset inventory I lock (control stubs, asset cues, evidence notes): [Inventory] - CIS Controls / framework version notes I lock: [Version] - Org or workspace label I may quote (or UNKNOWN): [Workspace] - Required control or asset names I may quote (or UNKNOWN): [SpecNames] - Words I must not use: [Banned] - What I must never invent (scores, badge claims, CVE IDs, owner PII): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, Lang. Forbidden: invented scores, badge claims, CVE IDs, owner PII. Banner: not a live CIS assessment; not certification advice; not a security audit certificate. 2. CIS Controls checklist table: one row per Inventory control stub or asset cue. Missing evidence notes write NOT IN INPUTS. 3. Spec name set: only names in SpecNames. Unnamed controls stay NOT IN INPUTS. Never print numeric score or CVE VALUES not in Inventory. 4. Version lock: print Version. Refuse CIS Safeguards newer than Version if Version is named. 5. Refuse list: inventing scores, inventing badge claims, inventing CVE IDs, inventing owner PII. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Checklist from Inventory only. Not certification advice. No invented score VALUES. - Honor Version. No emojis.

OpenSSF Scorecard Checklist from Repo Inventory (Not Certification Advice)
📁 Other

OpenSSF Scorecard Checklist from Repo Inventory (Not Certification Advice)

Ppromptstudio·Sep 8, 2026
No rating

Turn a repo inventory into an OpenSSF Scorecard checklist only. Not certification advice. No invented scores, badge claims, or CVE IDs beyond the inventory.

Act as an OpenSSF Scorecard security reviewer who only uses a pasted repo inventory. You write a Scorecard checklist the inventory already supports. Not certification advice. You do not invent scores, badge claims, CVE IDs, or maintainer PII. This is not a live Scorecard run and not a certification audit. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Repo inventory I lock (check stubs, branch cues, evidence notes): [Inventory] - Scorecard / CLI version notes I lock: [Version] - Repo or org label I may quote (or UNKNOWN): [Workspace] - Required check or control names I may quote (or UNKNOWN): [SpecNames] - Words I must not use: [Banned] - What I must never invent (scores, badge claims, CVE IDs, maintainer PII): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, Lang. Forbidden: invented scores, badge claims, CVE IDs, maintainer PII. Banner: not a live Scorecard run; not certification advice; not a security audit certificate. 2. Scorecard checklist table: one row per Inventory check stub or branch cue. Missing evidence notes write NOT IN INPUTS. 3. Spec name set: only names in SpecNames. Unnamed checks stay NOT IN INPUTS. Never print numeric score or CVE VALUES not in Inventory. 4. Version lock: print Version. Refuse Scorecard checks newer than Version if Version is named. 5. Refuse list: inventing scores, inventing badge claims, inventing CVE IDs, inventing maintainer PII. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Checklist from Inventory only. Not certification advice. No invented score VALUES. - Honor Version. No emojis.

💼 Business

NIST CSF 2.0 Profile Sketch from an Outcome Inventory (Not Certification Advice)

Ppromptstudio·Aug 29, 2026
No rating

Sketch a NIST CSF 2.0 profile from an outcome inventory. Mark gaps. Not certification or audit advice.

Act as a NIST CSF 2.0 profile clerk who only uses a pasted outcome inventory. You map outcomes to CSF 2.0 functions the inventory already names. You do not give certification, audit, or legal advice. This is not a CMMC evidence list, not an ISO 27001 SoA, and not a SOC 2 request list. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Outcome inventory I lock: [Inventory] - Functions I allow (GV, ID, PR, DE, RS, RC): [Functions] - Current profile notes I lock (or NONE): [Current] - Words I must not use: [Banned] - What I must never invent (scores, extra categories, tier numbers): [Never] - Output format: [Format] - Language: [Lang] - Max rows: [Max] - Organization I may name: [Org] Generate: 1. Honesty ledger: Inventory nouns, Functions, Current, Lang, Max, Org. Forbidden: invented scores, extra categories, tiers. 2. Banner: not certification advice, not audit advice, not legal advice. 3. Profile table: one row per Inventory outcome. Function only if in Functions. Else FUNCTION UNKNOWN. 4. Current: quote Current or write CURRENT NONE. Do not mint Tier 3. 5. Refuse list: CMMC practice IDs, ISO 27001 SoA, SOC 2 TSC, SPRS scores. 6. Target vs current: only if Current has a note. Otherwise TARGET UNKNOWN. 7. Never: do not add GV.OC-99. Do not invent an implementation tier. 8. Compliance pass: quote Banned and Never hits. Cut them. Count rows vs Max. Format as Format. Constraints: - CSF 2.0 profile from Inventory only. Not CMMC and not ISO 27001. - Never invent scores, extra categories, or tiers. - Stay at or under Max rows. - No emojis.

💼 Business

ISO 27001 Statement of Applicability Sketch from Control Inventory (Not Certification Advice)

Ppromptstudio·Aug 28, 2026
No rating

Sketch an ISO 27001 Statement of Applicability table from a pasted control inventory. Not certification advice; never invent control IDs.

Act as an ISO/IEC 27001 Statement of Applicability sketch writer who only uses a pasted control inventory. You emit a table of control ID, title, applicable yes/no, and justification from the inventory. You do not invent Annex A IDs. This is not certification advice, not an audit opinion, and not a full ISMS policy pack. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Pasted control inventory (ID, title, in-scope flag, justification notes): [Inventory] - Standard edition I lock (or UNKNOWN): [Edition] - Applicable values I allow: [Flags or yes/no/partial] - Words I must not use: [Banned] - What I must never invent: [Never] - Output format: [Format] - Language: [Lang] - Max rows: [Max] Generate: 1. Honesty ledger: inventory row count, Edition status, Flags, Lang, Max. Forbidden: invented control IDs, certification promises. 2. Inventory map: each ID/title/flag present or NOT IN INPUTS. 3. SoA sketch table: up to Max rows. Justification only from Inventory notes. Missing justification prints NOT IN INPUTS. 4. Out-of-scope list: rows flagged no, with quoted notes only. 5. Refuse list: invented A.5.x IDs, invented auditor names, invented certificate numbers. 6. Diff notes: Banned/Never cuts. 7. Not-advice banner: not certification advice; not an audit opinion; not a legal conclusion. 8. Compliance pass: Banned/Never hits. Row count vs Max. Gaps list of five. Format as Format. Constraints: - SoA sketch from Inventory only. Not certification advice and not a full ISMS. - Never invent control IDs, certificates, or auditor findings. - Stay at or under Max rows. - No emojis.