Importance of report writing for pen testersPEN-300: Advanced Evasion Techniques and Breaching Defenses (OSEP)
ã€è‡ªåˆ†ç”¨ãƒ¡ãƒ¢ã€‘プãƒã‚¸ã‚§ã‚¯ãƒˆãƒžãƒã‚¸ãƒ¡ãƒ³ãƒˆã®ãƒˆãƒªã‚»ãƒ„ã‚’èªã‚“㧠- Qiita
Deleted articles cannot be recovered. Draft of this article would be also deleted. Are you sure you want to delete this article? å‰æ 主ã«ãƒ—ãƒã‚¸ã‚§ã‚¯ãƒˆã‚’始ã‚ã‚‹å‰ã«æ„è˜/確èªã—ã¦ãŠããŸã„ã“ã¨ãŒå‚考ã«ãªã£ãŸãŸã‚ã€ãれらをä¸å¿ƒã«ã¾ã¨ã‚ã¦ã„ã‚‹ 今後æ„è˜ã—ã¦ã„ããŸã„ã“㨠部分最é©ã®é›†åˆä½“ã¯å…¨ä½“最é©ã«ã¯ãªã‚‰ãªã„ å„部門ã®åŠªåŠ›ã®æŠ•è³‡å¯¾åŠ¹æžœã‚’最大化ã™ã‚‹ãŸã‚ã«ã¯å…¨ç¤¾æœ€é©ã‚’考ãˆã‚‹ ãƒãƒ¼ãƒ ã¨çµ„ç¹”ã®ç›®æ¨™ã‚’åˆã‚ã›ã‚‹ ã‚„ã‚ŠãŸã„ã“ã¨ãŒã‚ã‚‹ã‹ã‚‰ãƒ—ãƒã‚¸ã‚§ã‚¯ãƒˆã‚’発足ã•ã›ã‚‹ã®ã§ãªãã€ä¸é•·æœŸã§è€ƒãˆã¦å…¨ä½“ã§å¿…è¦ã¨åˆ¤æ–ã—ãŸã‚‚ã®ã‚’プãƒã‚¸ã‚§ã‚¯ãƒˆã¨ã™ã‚‹ マトリックス組織(å°‚ä»»ã§ãªã兼務ã§ã‚„ã‚‹å ´åˆ)ã®å ´åˆã€ãã®ãƒ¡ãƒ³ãƒãƒ¼ã®å 有率をã®è¨ˆç”»æ®µéšŽã‹ã‚‰æ±ºã‚ã‚‹ プãƒã‚¸ã‚§ã‚¯ãƒˆé–‹å§‹ã®æ®µéšŽã§ä»¥ä¸‹ã‚„ã£ã¦ãŠã フェーズ分㑠ステークホ
Postmortem Template - PagerDuty Incident Response Documentation
Home Getting Started On-Call Being On-Call Who's On-Call? Alerting Principles Before an Incident What is an Incident? Severity Levels Different Roles Call Etiquette Complex Incidents During an Incident During an Incident External Communication Guidelines Security Incident After an Incident After an Incident Postmortem Process Postmortem Template Overview What Happened Contributing Factors Resoluti
「Ask What, not Why〠失敗ã—ãŸã¨ãã«è‡ªä¿¡ã‚’失ã„ã‹ã‘ãŸã‚‰å®Ÿè¡Œã—ã¦ã„るメンタル転è½å›žé¿è¡“ - Money Forward Developers Blog
åŠå¹´ã¶ã‚Šã®ã‚«ã‚コ……ã©ã‚‚……。気ã¥ã„ãŸã‚‰HRソリューション本部ã‹ã‚‰MFBC-CTO室ã«ç•°å‹•ã—ã¦ã„ãŸVTRyoã§ã™ã€‚兼任ã§å¼•ã続ãHRç³»ã®ãƒžãƒãƒ¼ãƒ•ã‚©ãƒ¯ãƒ¼ãƒ‰ クラウドシリーズも担当ã—ã¦ã„ã¾ã™ã€‚ ソフトウェアエンジニアã¨ã—ã¦ã®çµŒé¨“値ãŒå¢—ãˆã¦ãã‚‹ã¨ã€æ¬¡ç¬¬ã«ãƒ¬ãƒ“ュー担当者ã«ãªã‚‹ã“ã¨ãŒå¢—ãˆã¦ãã‚‹ã§ã—ょã†ã€‚ç§ãŒæ‰€å±žã™ã‚‹SREãƒãƒ¼ãƒ ã§ã‚‚Terraformã®ç›¸äº’レビューãŒé »ç¹ã«å®Ÿæ–½ã•ã‚Œã¦ã„ã¾ã™ã€‚ãã“ã§ã€äº‹ä»¶ã¯èµ·ããŸã®ã§ã™ã€‚ 自信をæŒã£ã¦Approveã—ãŸPull Requestã§æ¬¡ã€…ã«äº‹æ•…ãŒèµ·ãã¦ã—ã¾ã£ãŸ ç¾åœ¨HR内ã®ãƒžãƒãƒ¼ãƒ•ã‚©ãƒ¯ãƒ¼ãƒ‰ クラウドシリーズã¯ã€ãƒ¢ãƒ€ãƒ³ãªé–‹ç™ºåŸºç›¤ã¸ã¨ãƒªãƒ—レイス作æ¥ã‚’多ãè¡Œã£ã¦ã„ã¾ã™ã€‚ã“ã‚Œã¾ã§å‹•ã„ã¦ã„ãŸåŸºç›¤ã«æ„Ÿè¬ã—ã¤ã¤ã€æ–°ã—ã„Platformã¸ã¨ç§»è¡Œã—ã€æœ€çµ‚çš„ã«å…ƒã‚ã£ãŸãƒªã‚½ãƒ¼ã‚¹ã‚’削除ã—ã¾ã™ã€‚ 事件ã¯ã“㮠リソース削除 ã§èµ·ãã¾ã—ãŸã€‚ ãƒãƒ¼ãƒ 内レビュー OK リãƒã‚¸ãƒˆãƒªç®¡ç†è€…レビュー
ã‚ックオフã‹ã‚‰æŒ¯ã‚Šè¿”ã‚Šã¾ã§ã€‚ケースã«ã‚ã‚ã›ã¦ä½¿ãˆã‚‹ï¼ã‚¢ã‚¸ã‚§ãƒ³ãƒ€ãƒ†ãƒ³ãƒ—レート集 - COPILOT KNOWLEDGE
ã“ã‚“ã«ã¡ã¯ï¼SuperGoodMeetings カスタマーサãƒãƒ¼ãƒˆãƒãƒ¼ãƒ ã§ã™ã€‚ プãƒã‚¸ã‚§ã‚¯ãƒˆæŽ¨é€²ã‚’実ç¾ã™ã‚‹ã‚¯ãƒ©ã‚¦ãƒ‰ã‚µãƒ¼ãƒ“ス SuperGoodMeetings ã®é–‹ç™ºã‚’進ã‚ã¦ã„るコパイãƒãƒ„トã§ã¯ã€ã€Œå®šä¾‹ãƒŸãƒ¼ãƒ†ã‚£ãƒ³ã‚°ã€ã‚’活用ã™ã‚‹ã“ã¨ã‚’推奨ã—ã¦ã„ã¾ã™ã€‚ 定期的ã«é–‹å‚¬ã•ã‚Œã‚‹ãƒŸãƒ¼ãƒ†ã‚£ãƒ³ã‚°ã§ã€å„メンãƒãƒ¼ï¼ãƒãƒ¼ãƒ ã‹ã‚‰é€²æ—を共有ã—ã¦ã‚‚らã„ã€æŠ±ãˆã¦ã„る課題やトラブルã«ã¤ã„ã¦ç›¸è«‡ã€ãƒ¡ãƒ³ãƒãƒ¼å…¨å“¡ã§è°è«–・決定ã—ã¦ã„ãã“ã¨ã§ã€çŠ¶æ³ã«åˆã£ãŸãƒ—ãƒã‚¸ã‚§ã‚¯ãƒˆæŽ¨é€²ãŒå¯èƒ½ã«ãªã‚Šã¾ã™ã€‚ 定例ミーティングã¯ãƒ¡ãƒ³ãƒãƒ¼ã‚’集ã‚ã¦ã‚„ã¿ãã‚‚ã«é–‹å‚¬ã™ã‚‹ã ã‘ã§ã¯ãªãã€ã‚¢ã‚¸ã‚§ãƒ³ãƒ€ã‚’ã—ã£ã‹ã‚Šæº–å‚™ã—ã¦ãŠãã“ã¨ã€ã¾ãŸã€ãƒ¡ãƒ³ãƒãƒ¼ã®æœŸå¾…値をã™ã‚Šåˆã‚ã›ã‚‹ã€Œãƒãƒ¼ãƒ«ã‚»ãƒƒã‚·ãƒ§ãƒ³ã€ã‚„å–り組ã¿ã«ã¤ã„ã¦ã®ã€Œãµã‚Šã‹ãˆã‚Šã€ç‰ã‚’実施ã™ã‚‹ã“ã¨ãŒé‡è¦ã§ã™ã€‚ ã“ã“ã§ã¯ã€å®šä¾‹ãƒŸãƒ¼ãƒ†ã‚£ãƒ³ã‚°ã§ä½¿ãˆã‚‹ã€Žã‚¢ã‚¸ã‚§ãƒ³ãƒ€ãƒ†ãƒ³ãƒ—レートã€ã‚’紹介ã—ã¦ã„ãã¾ã™ã€‚ 「誰ãŒã€è©±ã™ã®ã‹ 「何をã€è°è«–ã—ãŸã„ã®ã‹
GitHub - golang-standards/project-layout: Standard Go Project Layout
This is a basic layout for Go application projects. Note that it's basic in terms of content because it's focusing only on the general layout and not what you have inside. It's also basic because it's very high level and it doesn't go into great details in terms of how you can structure your project even further. For example, it doesn't try to cover the project structure you'd have with something
å°‘ã—ãšã¤è‚²ã¦ã‚‹Go言語ã®ãƒ—ãƒã‚¸ã‚§ã‚¯ãƒˆæ§‹æˆ
23/9/21追記：ã“ã®è¨˜äº‹ã‚’èªã‚€å‰ã« ã¤ã„ã«Goãƒãƒ¼ãƒ ã‹ã‚‰ã€ãƒ—ãƒã‚¸ã‚§ã‚¯ãƒˆæ§‹æˆã«é–¢ã™ã‚‹ã‚¬ã‚¤ãƒ‰ãŒå…¬é–‹ã•ã‚Œã¾ã—ãŸï¼ 本記事をèªã‚“ã§ãã ã•ã‚‹ã“ã¨ã‚‚大変嬉ã—ã„ã§ã™ãŒã€ãœã²ã“ã¡ã‚‰ã®ã‚¬ã‚¤ãƒ‰ã‚‚ã”一èªãã ã•ã„ï¼ ã“ã®è¨˜äº‹ã¯ä½• Go言語を書ã„ãŸã“ã¨ãŒã‚る方もã€èˆˆå‘³ã¯ã‚ã‚‹ã‘ã©è§¦ã£ãŸã“ã¨ãŒãªã„方もã“ã‚“ã«ã¡ã¯ã€‚ Goã«é™ã£ãŸè©±ã§ã¯ãªã„ã¨æ€ã„ã¾ã™ãŒã€ã‚¬ãƒªã‚¬ãƒªã‚³ãƒ¼ãƒ‰ã‚’書ã„ã¦ã„ã¦ã€ã‚るタイミングã§æ°—ã«ãªã‚‹ã®ãŒãƒ—ãƒã‚¸ã‚§ã‚¯ãƒˆæ§‹æˆï¼ˆã“ã“ã§ã¯ãƒ‡ã‚£ãƒ¬ã‚¯ãƒˆãƒªæ§‹æˆã®æ„図）ã§ã¯ãªã„ã§ã—ょã†ã‹ï¼Ÿ ãれをè£ä»˜ã‘ã‚‹ã‹ã®ã‚ˆã†ã«ã€Go界隈ã§ã¯ä»¥ä¸‹ã®ãƒªãƒã‚¸ãƒˆãƒªãŒè©±é¡Œã«ä¸ŠãŒã‚‹ã“ã¨ãŒã‚ã‚Šã¾ã™ã€‚Staræ•°ã™ã”ã„ã§ã™ã😇 リãƒã‚¸ãƒˆãƒªåã‹ã‚‰å…¬å¼æ„ŸãŒæ¼‚ã„ã¾ã™ãŒã€ãã†ã„ã†è¨³ã§ã¯ãªã„ã®ãŒãƒŸã‚½ã§ã™ã€‚ ã“ã¡ã‚‰ã®ãƒªãƒã‚¸ãƒˆãƒªå†’é ã«ã‚‚記載ã•ã‚Œã¦ã„ã¾ã™ãŒã€æ¬¡ã®ç‚¹ã«ç•™æ„ã™ã‚‹å¿…è¦ãŒã‚ã‚‹ã§ã—ょã†ã€‚ ã“ã‚Œã¯ã€Goアプリケーションプãƒã‚¸ã‚§ã‚¯ãƒˆã®åŸºæœ¬çš„ãªãƒ¬ã‚¤ã‚¢ã‚¦ãƒˆã§ã™ã€‚ã“ã‚Œã¯ã€ã‚³ã‚¢ã¨
ChatGPTプãƒãƒ³ãƒ—トテンプレート例文集｜入江 æ…Žå¾ã®å€‹äººçš„ãªé–‹ç™ºðŸš€
ChatGPTã§æ–‡ç« を作æˆã—ã¦ã€æœ€å¾Œã«ã€Žæ–‡ç« を書ã時ã¯ä»¥ä¸‹ã®ãƒ«ãƒ¼ãƒ«ã‚’å¿ å®Ÿã«å®ˆã£ã¦ãã ã•ã„。ã€ã¨å…¥åŠ›ã™ã‚‹ã¨ã€è‡ªåˆ†ã®å¸Œæœ›é€šã‚Šã®æ–‡ç« を書ã„ã¦ãã‚Œã¾ã™ã€‚具体的ã«ã¯ã“ã‚“ãªæ„Ÿã˜ã§ã™â†“↓ pic.twitter.com/A4ABtkGN3u — ãƒŸã‚¹ãƒ†ã‚£ãƒ¼ï¼ å°‚æ¥ãƒ–ãƒã‚¬ãƒ¼ (@misty_blog) March 19, 2023 ChatGPTã§ã€Žã€‡ã€‡ 〇〇ã§æ¤œç´¢ã™ã‚‹ãƒ¦ãƒ¼ã‚¶ãƒ¼ãŒæ€ã‚ãšã‚¯ãƒªãƒƒã‚¯ã—ã¦ã—ã¾ã†ãƒ–ãƒã‚°è¨˜äº‹ã®ãƒªãƒ¼ãƒ‰æ–‡ã‚’〇〇ã®ãƒ—ãƒç›®ç·šã§æ›¸ã„ã¦ãã ã•ã„ã€ã¨æŒ‡ç¤ºã™ã‚‹ã¨ã€SEOã§ä¸Šä½è¡¨ç¤ºã§ãるレベルã®ã€Žãƒªãƒ¼ãƒ‰æ–‡ã€ãŒç°¡å˜ã«æ›¸ã‘ã¦ã—ã¾ã†ã€‚詳ã—ã„ã‚„ã‚Šæ–¹ã¯ã“ã‚“ãªæ„Ÿã˜ã§ã™â†“ pic.twitter.com/e2wweMLfkr — ãƒŸã‚¹ãƒ†ã‚£ãƒ¼ï¼ å°‚æ¥ãƒ–ãƒã‚¬ãƒ¼ (@misty_blog) March 22, 2023
Shell Script Best Practices — The Sharat's
This article is about a few quick thumb rules I use when writing shell scripts that I’ve come to appreciate over the years. Very opinionated. Things¶ Use bash. Using zsh or fish or any other, will make it hard for others to understand / collaborate. Among all shells, bash strikes a good balance between portability and DX. Just make the first line be #!/usr/bin/env bash, even if you don’t give exec
ä¼ç”»ãƒ»æ案・見ç©ãƒ»ç´å“・契約ãªã©ã®ãƒ†ãƒ³ãƒ—レ・知è˜ã¾ã¨ã‚２３ | コムテブãƒã‚°
TL;DR クライアントã•ã‚“ã¨ã®æ‰“ã¡åˆã‚ã›ã‚„会è°ã®å¾Œã¯ã€å¿…ãšè°äº‹éŒ²ã‚’書ã„ã¦ç¤¾å†…共有ã—ã¾ã™ã€‚座ã£ãŸä½ç½®ã‚„発言ãªã©ã‚‚ã€æ€ã„出ã—ãªãŒã‚‰ç°¡æ½”ã«æ›¸ãã¾ã™ã€‚ãŠã‹ã’ã§ã€Œä½•ã‚’話ã—ãŸã£ã‘？ã€ã€Œè¨€ã£ãŸã€è¨€ã‚ãªã„ã€ã‚’防ã’ã¦ã¾ã™ã€‚フリーランスã®äººã¯ã€è¦‹ç©æ›¸ã€è«‹æ±‚書ã€å¥‘約書ã€æ³•å¾‹ãªã©ã®ãƒ†ãƒ³ãƒ—レや知è˜ãŒã‚ã‚‹ã¨ã€ã‚¹ãƒ ーズã«å…ˆã¸é€²ã‚ã¾ã™ã€‚ãã®ä»–ã€ãƒ’アリングシートã€å¥‘約書ãªã© Web 制作æ¥ã§ãƒªã‚¢ãƒ«ã§å¿…è¦ã ã£ãŸæ›¸é¡žç³»ãƒ†ãƒ³ãƒ—レや知è˜ã‚’ã¾ã¨ã‚ã¾ã—ãŸã€‚ ä¼ç”»ï¼æ案 １．ä¼ç”»æ›¸ ä¼ç”»æ›¸ã¯ã©ã‚Œãらã„ã®ã‚³ã‚¹ãƒˆã§åŠ¹æžœï¼ˆå£²ä¸Šï¼‰ã‚’å¾—ã‚‹ã‹ã¨ã„ã†ã®ãŒä¸€ç•ªå¤§åˆ‡ã€‚ã¨ã¯ã„ãˆã€ä¸Šå¸ã‚’説得ã§ãã‚‹ä¼ç”»æ›¸ã‚‚大切。以下ã¯ä¼ç”»æ›¸ã®ä½œã‚Šæ–¹ã¨è³‡æ–™ä½œæˆã‚µãƒ¼ãƒ“スãªã©ã®ã¾ã¨ã‚ã§ã™ã€‚ [ä¿å˜ç‰ˆ] 最強ã®ä¼ç”»æ›¸ã®ä½œã‚Šæ–¹ã¨è³‡æ–™ä½œæˆã‚µãƒ¼ãƒ“ス完全ã¾ã¨ã‚ | 世界ã‚ã “通るä¼ç”»æ›¸â€ä½œã‚Šã®åŸºæœ¬ï¼ä¸Šå¸ã‚’説得ã§ãã‚‹ä¼ç”»è³‡æ–™ã®ä½œã‚Šæ–¹è¬›åº§#1 | Web 担当者 Forum ２．æ案書 æ案
技術文書ã®æ›¸ãæ–¹
howto-tech-docs.md 技術文書ã®æ›¸ãæ–¹ ã“ã®ãƒ¡ãƒ¢ã¯ã€ç§ï¼ˆ@ymmt2005）ãŒé•·å¹´ã«ã‚ãŸã£ã¦ã‚½ãƒ•ãƒˆã‚¦ã‚§ã‚¢ãƒ—ãƒãƒ€ã‚¯ãƒˆé–‹ç™ºã«é–¢ã‚ã£ã¦ã㦠2022å¹´ç¾åœ¨ã“ã†ã—ãŸã»ã†ãŒè‰¯ã„ã¨è€ƒãˆã¦ã„るベストプラクティスã§ã™ã€‚ 科å¦çš„ãªåˆ†æžç‰ã«åŸºã¥ãã‚ã‘ã§ã¯ãªã„経験則ã§ã‚ã‚‹ãŸã‚ã€ä»Šå¾Œã‚‚éšæ™‚見直ã™ã“ã¨ãŒã‚ã‚Šã¾ã™ã—〠ã“ã“ã«æ›¸ã„ã¦ã‚ã‚‹ã“ã¨ãŒå¸¸ã«æ£ã—ã„ã‚ã‘ã§ã‚‚ã‚らゆるソフトウェア開発ã«é©ã™ã‚‹ã‚ã‘ã§ã‚‚ã‚ã‚Šã¾ã›ã‚“。 ã—ã‹ã—ãªãŒã‚‰ã€å®Ÿå‹™çµŒé¨“ãŒè±Šå¯Œã§ã€ãƒ¢ãƒ€ãƒ³ãªæŠ€è¡“スタックã«æ˜Žã‚‹ã„エンジニアã®çµŒé¨“則ã¯ä¸€å®šã® å½¹ã«ç«‹ã¤ã®ã§ã¯ãªã„ã‹ã¨è€ƒãˆã¦è¨˜ã—ã¾ã™ã€‚ 技術文書ã¨ã¯ ã“ã“ã§ã¯ã€ã‚½ãƒ•ãƒˆã‚¦ã‚§ã‚¢é–‹ç™ºã§æŠ€è¡“者ãŒæ›¸ãã¹ã文書ã¨ã„ã†ã“ã¨ã«ã—ã¾ã™ã€‚ ソフトウェアエンジニアã«ã‚‚役割ãŒã„ã‚ã„ã‚ã‚ã‚Šã€ã‚¢ãƒ¼ã‚テクト㨠independent contributor ã§ã¯æ›¸ã文書ãŒé•ã†ã¨ã„ã†ã“ã¨ã¯ã‚ã‚‹ã§ã—ょã†ã‘ã‚Œã©ã€ã“ã“ã§ã¯ã”ã£ã¡ã‚ƒã«ã—ã¾ã™ã€‚
Jekyll • Simple, blog-aware, static sites
No more databases, comment moderation, or pesky updates to install—just your content. How Jekyll works → Static Markdown, Liquid, HTML & CSS go in. Static sites come out ready for deployment. Jekyll template guide → Blog-aware Permalinks, categories, pages, posts, and custom layouts are all first-class citizens here. Migrate your blog →
ランã‚ング
障害
ランã‚ング
リリースã€éšœå®³æƒ…å ±ãªã©ã®ã‚µãƒ¼ãƒ“スã®ãŠçŸ¥ã‚‰ã›
最新ã®äººæ°—エントリーã®é…ä¿¡
j次ã®ãƒ–ックマーク
kå‰ã®ãƒ–ックマーク
lã‚ã¨ã§èªã‚€
eコメント一覧を開ã
oページを開ã
GitHub - shahedbd/awesome-project-management: Awesome lists about Project Management interesting and useful topics.
ProjectDiscovery
GitHub - breaking153/GLAN-NucleiFinger: Nuclei指纹集åˆï¼ˆè‡ªç”¨ï¼‰
GitHub - whoissecure/yaset-templates: Templates for Yaset (https://github.com/whoissecure/yaset)
GitHub - whoissecure/yaset: Yet Another Subdomain Enumeration Tool, a template based tool to enumerate subdomains passively.
ChatGPT Templates
Attacking and Enumerating Joomla | HackerTarget.com
How I found 130+ Sub-domain Takeover vulnerabilities using Nuclei
{{#tags}}- {{label}}
{{/tags}}