Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[ BUG ] Import-FalconConfig generates IoaRule or IoaGroup property-related error #446

Open
bk-cs opened this issue Jan 14, 2025 · 1 comment
Assignees
Labels
bug Something isn't working fix available Self-applied fix available in issue

Comments

@bk-cs
Copy link
Collaborator

bk-cs commented Jan 14, 2025

Describe the bug
When importing IoaRule, a The property 'enabled' cannot be found on this object error is generated, or you may be prompted to enter a comment when an IoaRule is being created.

When modifying an IoaGroup a 400: rule group version missing error may appear.

To Reproduce
Use Import-FalconConfig with IoaGroup.

Expected behavior
The IoaRule should add enabled properties when they are required, and append a comment automatically, when necessary. If modifying an IoaGroup, a proper version should be automatically supplied.

Environment (please complete the following information):

  • PSFalcon: 2.2.8
@bk-cs bk-cs added the bug Something isn't working label Jan 14, 2025
@bk-cs bk-cs self-assigned this Jan 14, 2025
@bk-cs bk-cs changed the title [ BUG ] Import-FalconConfig generates IoaRule property or comment related error [ BUG ] Import-FalconConfig generates IoaRule or IoaGroup property-related error Jan 14, 2025
@bk-cs
Copy link
Collaborator Author

bk-cs commented Jan 14, 2025

Changes have been added to the next release to resolve this issue. If you'd like to resolve it for your local module before release, you can replace public\psf-config.ps1 using the steps outlined below.

Import-Module -Name PSFalcon
$ModulePath = (Show-FalconModule).ModulePath
(Invoke-WebRequest -Uri https://raw.githubusercontent.com/CrowdStrike/psfalcon/f97df4b4933f8051b1a44ccf46c6758b1bfa53f8/public/psf-config.ps1 -UseBasicParsing).Content > (Join-Path (Join-Path $ModulePath public) psf-config.ps1)

Please ensure that you close and re-open PowerShell and re-import PSFalcon before testing.

@bk-cs bk-cs added the fix available Self-applied fix available in issue label Jan 14, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working fix available Self-applied fix available in issue
Projects
None yet
Development

No branches or pull requests

1 participant