You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Judging from the StackOverflow questions, it appears to me that custom log files implementations are more often used then the native Start-Transcript cmdlet and suspect that this is due to the fact enterprise companies (as the one I am working for) want their own logging facilities which might be a specific log format (e.g. including a specific time stamp per entry) up till writing (specific) entries to a database.
A -Script <ScriptBlock> parameter that refers to a script that is called at each logging event. Within the script (which might need to run in a different scope), I would expect to have access to information (via current item ($_)?) as:
A reference to thr output streams since last event
The timestamp of the event (basically the current time)
Transcript properties/parameters (as the Path if supplied)
This feels like a reasonable request for some kind of logging provider mechanism for transcripts. But we need to think carefully about how this could be abused for information disclosure.
@WG-Security
Working security group discussed this and have concerns about inadvertently exposing sensitive information to arbitrary providers, that may move the data off-box. PowerShell transcripts captures all data written to the console, which can include secrets, and therefore it is more sensitive to where that data goes. If we implemented a transcript collection provider architecture, we would have to also include some sort of encryption scheme.
@PowerShell/wg-powershell-engine reviewed this. We think transcripts are best suited to auditing rather than log writing (even with the proposal to bring it closer to logging).
That said, a custom Out-Default or even PSHost implementation could accomplish similar results as the proposal (though slightly more involved).
Activity
PaulHigin commentedon Jun 27, 2022
This feels like a reasonable request for some kind of logging provider mechanism for transcripts. But we need to think carefully about how this could be abused for information disclosure.
PaulHigin commentedon Jul 18, 2022
@WG-Security
Working security group discussed this and have concerns about inadvertently exposing sensitive information to arbitrary providers, that may move the data off-box. PowerShell transcripts captures all data written to the console, which can include secrets, and therefore it is more sensitive to where that data goes. If we implemented a transcript collection provider architecture, we would have to also include some sort of encryption scheme.
SeeminglyScience commentedon Sep 19, 2023
@PowerShell/wg-powershell-engine reviewed this. We think transcripts are best suited to auditing rather than log writing (even with the proposal to bring it closer to logging).
That said, a custom
Out-Defaultor evenPSHostimplementation could accomplish similar results as the proposal (though slightly more involved).microsoft-github-policy-service commentedon Sep 21, 2023
This issue has been marked as declined and has not had any activity for 1 day. It has been closed for housekeeping purposes.